On Tuesday, January 29, 2008 11:51 AM -0500 Brian Mathis
<[EMAIL PROTECTED]> wrote:
There are some cases when you might want apache to be able to write to
files, but those are less frequent, so you should only change those
specific files to apache ownership, or change the group permissions to
a
Jim Perrin a écrit :
If apache owns everything in that directory, then it can modify them.
This can potentially be undesirable. Depending on what you're doing,
you'll have to mix and match permissions as needed. Mostly apache just
needs to be able to read stuff, so having root own it with 644 is
On Tue, Jan 29, 2008 at 11:25 AM, Niki Kovacs <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm currently setting up a simple web server. So far, everything (PHP,
> MySQL) works very well, but I admit I never gave security that much
> thought. Time to change that habit.
>
> First things first. The RHEL
On Jan 29, 2008 11:25 AM, Niki Kovacs <[EMAIL PROTECTED]> wrote:
> As far as I understand, I have to chown all my web content accordingly,
> so that everything below /var/www/html belongs to apache:apache. Right?
You can, but but I would only recommend doing that where the webserver
itself will b
Hi,
I'm currently setting up a simple web server. So far, everything (PHP,
MySQL) works very well, but I admit I never gave security that much
thought. Time to change that habit.
First things first. The RHEL Deployment Guide lists Apache's
configuration directives alphabetically. Instead of
5 matches
Mail list logo
