entry for osComerce.info?

[osc_svendsen]

IMHO it would be nice if osCommerce.info had an explanation as to:

1. How to determine whether it's chmod 644 or 744 that's relevant to you (or in ms3 install have detemin/do it for you?)

2. Exactly which files need to have what properties in the grafical presentation concerning all files / folders

from

Owner | Group | Public

Read X X X

Write

Execute

through

Owner | Group | Public

Read X X X

Write X X X

Execute X X X

(the 'cosmetic' whitespace ain't allowed)

 

All concerns about this question would then be taken care of from the kb.

 

I've never had the need to secure a web like the osCommerce-admin so actually new with the .htaccess-password and password-file and get surpriced that the pswfile actually needs 'readability' from public. (doh! so that's why it didn't work :-" )

[siavash]

IMHO it would be nice if osCommerce.info had an explanation as to:

1. How to determine whether it's chmod 644 or 744 that's relevant to you (or in ms3 install have detemin/do it for you?)

2. Exactly which files need to have what properties in the grafical presentation concerning all files / folders

from

            Owner | Group | Public

Read        X          X        X

Write       

Execute

through

            Owner | Group | Public

Read        X          X          X

Write        X          X          X

Execute    X          X          X

(the 'cosmetic' whitespace ain't allowed)

 

All concerns about this question would then be taken care of from the kb.

 

I've never had the need to secure a web like the osCommerce-admin so actually new with the .htaccess-password and password-file and get surpriced that the pswfile actually needs 'readability' from public. (doh! so that's why it didn't work :-" )

<{POST_SNAPBACK}>

 

yes i agree!

[siavash]

below is a good tutorial of CHMOD and read-write-access permossion settings:

 

http://catcode.com/teachmod/

 

and since we osc uses php you will need the following too:

 

http://uk2.php.net/chmod

 

hope it is clearer now.