I'm not saying you have to become root. I'm simply saying that for some
people it's a temptation ("If I change this to root, I don't have to worry
about ownership problems ever again").
6:21pm, Vladimir D Belousov wrote:
Why root? Just the user who has permissions to do something.
Paul Archer w
Why root? Just the user who has permissions to do something.
Paul Archer wrote:
Beware that this can be a fix that causes more problems. It's very
tempting to let the web server run as root--which opens up a big can
of security worms.
Paul
11:25am, Vladimir D Belousov wrote:
... But if you have
Beware that this can be a fix that causes more problems. It's very tempting
to let the web server run as root--which opens up a big can of security
worms.
Paul
11:25am, Vladimir D Belousov wrote:
... But if you have enabled SuEXEC (see the output `httpd -l`), your script
will run as user/group
... But if you have enabled SuEXEC (see the output `httpd -l`), your
script will run as user/group you specify.
Paul Archer wrote:
This is a very common problem. When you run the script from the
command line, you are running it with different privileges and a
different path than when the web se
... But if you have enabled SuEXEC (see the `httpd -l` output), your CGI
scripts will run as user/group you specify.
Paul Archer wrote:
This is a very common problem. When you run the script from the
command line, you are running it with different privileges and a
different path than when the w
This is a very common problem. When you run the script from the command
line, you are running it with different privileges and a different path than
when the web server runs it.
Most likely, either the command is not in the path for CGI scripts (try
setting $ENV{PATH} or calling the command with
