Security risks in setting public_html to 777?
From: Andy Bates (bates_at_mac.com)
Date: 04/01/04
- Next message: Jem Berkes: "Re: Block access that is too fast with iptables"
- Previous message: Tim Haynes: "Re: identd log entries"
- Next in thread: Baho Utot: "Re: Security risks in setting public_html to 777?"
- Reply: Baho Utot: "Re: Security risks in setting public_html to 777?"
- Reply: Joe: "Re: Security risks in setting public_html to 777?"
- Reply: Steve Wolfe: "Re: Security risks in setting public_html to 777?"
- Reply: NeoSadist: "Re: Security risks in setting public_html to 777?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 31 Mar 2004 15:15:21 -0800
I'm running a web server, and I want some CGI scripts to be able to
create files and directories in public_html. To do this, I need to set
permissions for public_html to 777. Are there any security risks in
doing this?
Previously, I had the CGI scripts writing to subdirectories of
public_html, and those were set to 777, although public_html was still
set to 755. Is that the best option, or can I change public_html
without introducing huge security holes?
Thanks for any suggestions!
Andy Bates.
- Next message: Jem Berkes: "Re: Block access that is too fast with iptables"
- Previous message: Tim Haynes: "Re: identd log entries"
- Next in thread: Baho Utot: "Re: Security risks in setting public_html to 777?"
- Reply: Baho Utot: "Re: Security risks in setting public_html to 777?"
- Reply: Joe: "Re: Security risks in setting public_html to 777?"
- Reply: Steve Wolfe: "Re: Security risks in setting public_html to 777?"
- Reply: NeoSadist: "Re: Security risks in setting public_html to 777?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|