From: Gert Menke <gert@menke.za.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo observations
Date: Sun, 10 Mar 2002 15:22:33 +0100 [thread overview]
Message-ID: <20020310142233.GB2332@mouse.mydomain> (raw)
In-Reply-To: <20020310134329.GA862@powerhouse>
Hi,
On Sun, Mar 10, 2002 at 07:43:29AM -0600, mrfab@arn.net wrote:
> I'd hesitate to go for root:www because there is always that possibility
> that php or mod_perl or just developer error in a script could allow a
> web user to overwrite a file--and with root permissions that could be a
> disaster.
Oh, I'm sorry. I was talking about the files when I said root:www. My httpd
runs as nobody:www. Or are you talking about files with the SUID bit set?
Greetings
Gert
next prev parent reply other threads:[~2002-03-10 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 3:11 [gentoo-dev] Gentoo observations mrfab
2002-03-10 3:29 ` Matthew Kennedy
2002-03-10 9:39 ` Gert Menke
2002-03-10 13:43 ` mrfab
2002-03-10 14:22 ` Gert Menke [this message]
2002-03-10 15:03 ` mrfab
2002-03-10 18:13 ` [gentoo-dev] how to add new Language specific Symbol? Corvus Corax
2002-03-11 16:27 ` [gentoo-dev] Gentoo observations Karl Trygve Kalleberg
2002-03-12 20:30 ` [gentoo-dev] I needed to remerge cvs after zlib update Brent Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020310142233.GB2332@mouse.mydomain \
--to=gert@menke.za.net \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox