[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] CGI above the /web directory...
- Subject: Re: [cobalt-users] CGI above the /web directory...
- From: Alisa Young <ayoung@xxxxxxxxxxxxx>
- Date: Thu Aug 30 10:28:36 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
on 8/30/01 5:54 PM, Dan Kriwitsky at webhosting@xxxxxxxxx wrote:
>>> I know this issue has been discussed to some degree in the archives...
>>> But the reason I post it again is because I found a lot of
>> contradicting and
>>> mis-information...
>>> Can someone (who had done it successfully) please offer advice
>> on the proper
>>> way to setup a cgi directory above the /web directory.
>>
>>
>> ScriptAlias /cgi-bin/ /home/sites/site#/cgi-bin/
>> AddHandler cgi-script .cgi
>> AddHandler cgi-script .pl
>>
>
> I'm trying to understand what the point of doing this is? Is it for
> security?
> With the scriptalias can't anyone still browse to
> www.domain.com/cgi-bin/file.ext and just get pointed to the
> /home/sites/site#/cgi-bin/ instead of /home/sites/site#/web/cgi-bin/
>
> I could see doing this with a cgi-bin someplace on the server and a script
> alias tag in all sites pointing to that for a global cgi-bin or a shared
> cgi-bin for sites created outside of the GUI.
> --
> Dan Kriwitsky
>
>
Personally, I found that if I create or use scripts for clients I just
create a directory called "cgi" in their web directory chown the directory
to root and chown the files within to admin/chmod 700. This keeps the
clients from downloading it, accidentally deleting it or overwriting.
Just my thoughts.
Alisa
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>