From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo location for squirrelmail attachments
Date: Fri, 09 Dec 2011 11:09:07 -0500 [thread overview]
Message-ID: <4EE232A3.7020902@orlitzky.com> (raw)
In-Reply-To: <CAN0CFw39fDRC-EYxP16yv3bQw-ePSCTiWvsVbL9LWeRbuLM_ng@mail.gmail.com>
On 12/09/2011 10:49 AM, Grant wrote:
>
> There is a Squirrelmail document recommending that the Squirrelmail
> data and attachments directories are established outside of the web
> server's reach. /var is given as an example.
The two aren't mutually exclusive; using the previous example, we have,
php_admin_value upload_tmp_dir /var/www/example.com/www/tmp
DocumentRoot /var/www/example.com/www/public
so Apache can't serve up the temporary files. But sticking them both
under /var/www/example.com/www does allow you to use tighter
open_basedir restrictions.
> This is a little disturbing because my Squirrelmail data directory was
> created under the webroot as apache:apache 0755 at some point. Would
> this have been done by Gentoo? Should I file a bug?
I'm not sure. There's probably a policy that says one of two things:
1. Ebuilds should by default set up everything as securely as
possible, or
2. Ebuilds should not mess with upstream
I've honestly never used Gentoo's webapp stuff; it confuses the hell out
of me.
next prev parent reply other threads:[~2011-12-09 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 19:17 [gentoo-user] Gentoo location for squirrelmail attachments Grant
2011-12-08 19:37 ` Stroller
2011-12-09 6:51 ` J. Roeleveld
2011-12-09 15:51 ` Grant
2011-12-09 16:08 ` Joost Roeleveld
2011-12-09 2:49 ` Michael Orlitzky
2011-12-09 15:49 ` Grant
2011-12-09 16:09 ` Michael Orlitzky [this message]
2011-12-09 16:14 ` Joost Roeleveld
2011-12-09 18:24 ` Grant
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=4EE232A3.7020902@orlitzky.com \
--to=michael@orlitzky.com \
--cc=gentoo-user@lists.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