This is something I asked before, like one or two years ago. I just want
to see if a solution has come up since then.
The problem is that with the normal (linux-distro) installation of apache
and mod_perl, all processes for all active scripting (cgi, perl, PHP..)
run as the same user. Thus, if
Joel Palmius wrote:
This is something I asked before, like one or two years ago. I just want
to see if a solution has come up since then.
The problem is that with the normal (linux-distro) installation of apache
and mod_perl, all processes for all active scripting (cgi, perl, PHP..)
run as the
Hello Joel Palmius,
Thursday, July 31, 2003, 3:12:02 PM, you wrote:
JP This is something I asked before, like one or two years ago. I just want
JP to see if a solution has come up since then.
JP The problem is that with the normal (linux-distro) installation of apache
JP and mod_perl, all
From: Joel Palmius [EMAIL PROTECTED]
Date: Thu, 31 Jul 2003 11:12:02 +0200 (CEST)
The question is, what is the state-of-the-art approach for protecting data
written to a file by mod_perl from being overwritten by an untrusted user?
Is it possible to run all mod_perl things as a separate user
Hello,
JPThe question is, what is the state-of-the-art approach for protecting data
JPwritten to a file by mod_perl from being overwritten by an untrusted user?
JPIs it possible to run all mod_perl things as a separate user (without
JPhaving to keep two parallel apache installations)?
pYou don't
