From: "Chris L. Mason" <clmason@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-root emerges
Date: Fri, 1 Oct 2004 13:01:26 -0300 [thread overview]
Message-ID: <610e346604100109013965fd8e@mail.gmail.com> (raw)
In-Reply-To: <200410011130.54994.pauldv@gentoo.org>
On Fri, 1 Oct 2004 11:30:42 +0200, Paul de Vrieze <pauldv@gentoo.org> wrote:
...
> Sandbox should never ever be regarded as a security measure. It isn't. It
> is almost trivial to subvert the sandbox. The reason for it's
> effectiveness is solely that it's purpose is to protect against
> accidental installing outside of the destination directory and so
> subverting the package management (in short protecting against bad
> makefiles and ebuilds). It IS NOT SECURE.
>
So, if builds (and installs to temporary target) were done as a
regular user, wouldn't that obviate the need for a sandbox at all?
Also, this would make things a lot safer on macos (and presumably
BSD), where the sandbox does not work.
Thanks,
Chris
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-01 16:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 13:24 [gentoo-dev] Non-root emerges Chris L. Mason
2004-09-30 13:28 ` Ciaran McCreesh
2004-09-30 13:39 ` Chris L. Mason
2004-09-30 14:04 ` Paul de Vrieze
2004-09-30 16:20 ` Luke-Jr
2004-09-30 16:38 ` Stephen P. Becker
2004-09-30 16:45 ` Paul de Vrieze
2004-09-30 17:50 ` Simon Stelling
2004-09-30 18:39 ` Chris L. Mason
2004-09-30 18:40 ` Stephen P. Becker
2004-09-30 18:48 ` Chris L. Mason
2004-09-30 19:04 ` Stephen P. Becker
2004-09-30 19:17 ` Chris L. Mason
2004-09-30 19:21 ` Stephen P. Becker
2004-09-30 19:55 ` Ned Ludd
2004-10-01 9:30 ` Paul de Vrieze
2004-10-01 16:01 ` Chris L. Mason [this message]
2004-10-01 16:56 ` Alin Nastac
2004-10-01 16:57 ` Ciaran McCreesh
2004-10-01 21:41 ` Ned Ludd
2004-10-01 21:55 ` Chris L. Mason
2004-10-01 1:57 ` Christian Birchinger
2004-09-30 18:58 ` Stroller
2004-10-18 3:56 ` Ed Grimm
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=610e346604100109013965fd8e@mail.gmail.com \
--to=clmason@gmail.com \
--cc=gentoo-dev@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