Unix Webcat Permission - Suggestions
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29295
interpreted = N
texte = Caveats: I do not work for SmithMicro and have picked up all of my Unix admin skills from reading man pages and O'Reilly books (the traditional method). I am running Unix Apache Module version 3.06f (since I like to perform my own installs, thanks). I tested this all with a clean install.Several users have asked for advice on permission settings and security. My best advice is to make _all_ files owned by nobody, and _all_ directories containing those files owned by nobody. This includes all webcatalog files/directories as well as user templates and databases. This is the normal operating methodology for Unix daemons. You also should not give any rights to any other user. In other words: chown -R nobody:nobody * #recursively set owner chmod -R go= * #set user/group rights to noneThis is not a security concern once you realize that the nobody user has no rights to directly log in. Unix security hacks that prey on the nobody user rely on tricking the O/S into upgrading nobody to root, or get some process running as root to run bad code.If you need to be FTP'ing files up to the server, work with your Unix administrator to create a SUID script that copies the files into the correct location and sets their owner and rights to the above. If you follow the above suggestions, an ordinary user cannot even list the files in your WebCat directories, let alone read them. The WebCat process will serve them up fine. Ordinary users should never have direct access to WebCatalog served files (IMHO). Once a fully multiuser WebCat daemon comes out (4.2?) that will change, but until then, anyone hosting WebCat will need to change rights/owners for all files.I am thinking in the back of my head about a small WebCat application which would facilitate managing multiple users/sites. Think about an admin database with username, pathname source, and destination. One button update would copy the source files to the destination, with the correct rights. I could even see a trigger to automate it (though I do not trust outside developers enough to copy their templates onto my server without looking at them). Users would only need ordinary rights to their parallel directory structure and WebCat would only run the versions in the official directories.HTHJohn Peacock ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
Caveats: I do not work for SmithMicro and have picked up all of my Unix admin skills from reading man pages and O'Reilly books (the traditional method). I am running Unix Apache Module version 3.06f (since I like to perform my own installs, thanks). I tested this all with a clean install.Several users have asked for advice on permission settings and security. My best advice is to make _all_ files owned by nobody, and _all_ directories containing those files owned by nobody. This includes all webcatalog files/directories as well as user templates and databases. This is the normal operating methodology for Unix daemons. You also should not give any rights to any other user. In other words: chown -R nobody:nobody * #recursively set owner chmod -R go= * #set user/group rights to noneThis is not a security concern once you realize that the nobody user has no rights to directly log in. Unix security hacks that prey on the nobody user rely on tricking the O/S into upgrading nobody to root, or get some process running as root to run bad code.If you need to be FTP'ing files up to the server, work with your Unix administrator to create a SUID script that copies the files into the correct location and sets their owner and rights to the above. If you follow the above suggestions, an ordinary user cannot even list the files in your WebCat directories, let alone read them. The WebCat process will serve them up fine. Ordinary users should never have direct access to WebCatalog served files (IMHO). Once a fully multiuser WebCat daemon comes out (4.2?) that will change, but until then, anyone hosting WebCat will need to change rights/owners for all files.I am thinking in the back of my head about a small WebCat application which would facilitate managing multiple users/sites. Think about an admin database with username, pathname source, and destination. One button update would copy the source files to the destination, with the correct rights. I could even see a trigger to automate it (though I do not trust outside developers enough to copy their templates onto my server without looking at them). Users would only need ordinary rights to their parallel directory structure and WebCat would only run the versions in the official directories.HTHJohn Peacock ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
jpeacock@univpress.com
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Alpha List for Catagory (1998)
WebCat2b15MacPlugin - showing [math] (1997)
includes and cart numbers (1997)
exclusive db lock with webcat-3 ? (2000)
Multiple catalog databases and showcart (1997)
4.5.1 upgrade fee (2003)
shipCost formula (1997)
question: back button prevention (1997)
What am I missing (1997)
Email (1998)
Great product and great job ! (1997)
RAM variables (1997)
textarea inputs and returns (1999)
quantity minimum problem (1997)
URL'ed value not written to DB URL'ed (2003)
Where's Cart Created ? (1997)
Show if time tags (1997)
Multi Actions (1999)
[Q] Novice's question (1997)
OK, here goes... (1997)