
February 18th, 2002, 06:33 PM
|
|
Contributing User
|
|
Join Date: Jan 2001
Posts: 5
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
When your ShopSite Shopping cart program tells you to put non CGI stuffs into your cgi-bin directory, I have to tell you not to use them, because their software is probably not written with security in mind.
What is cgi-bin for?
That's a centralize location for you to place all your CGI scripts into, so CGI scripts don't reside all over your docroot.
When your cgi-bin is ScriptAlias'ed, this enforces you to follow cgi-bin security standard. That is, you cannot place anything beside true CGI scripts into your cgi-bin directory, no nav.gif, no env.php, no .htaccess, no .htpasswd, no foobar.html and only true CGI scripts, nothing else.
>> how to allow additional directories (mainly the cgi-bin) to have .htaccess and .htpasswd abilities
You should place your .htpasswd above your docroot. You also don't need .htaccess because things that you put in .htaccess can always be defined in httpd.conf. If you must place them in cgi-bin, just don't ScriptAlias your cgi-bin directory and give it a Options +ExecCGI.
When you need to put non-CGI scripts or mkdir a directory under cgi-bin, why bother to use cgi-bin in the first place, as that defeats the whole security purpose for making a ScriptAlias directive.
|