Right. But, having access to files _created_ by the webserver is proabably what the sysadmin is trying to avoid... if you don't have permissions, don't have the access to change the permissions, are you sure you'll be allowed to run setuid scripts?
Paris Sinclair | 4a75737420416e6f74686572
pariss@efn.org | 205065726c204861636b6572
I wear my Geek Code on my finger.
| [reply] |
Yeah, this is in intranet project and security is not a big
issue. I'm in total control.
| [reply] |
You might still want to keep an eye on security considerations like this. Not so much because you're worried about someone deliberately breaking into the site (although there are some companies where I would...) but simply because it makes it easier for someone to accidently break the site. Users can do the damndest things, and it wouldn't be the first time a "little permissions hole" ended in a deleted site through an innocent mistake.
- email Ozymandias
| [reply] |
The only way that you can be in total control of the program is if you're the only person ever using it.
| [reply] |