From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Reviving the Sandbox project
Date: Fri, 22 Sep 2017 18:01:48 -0400 [thread overview]
Message-ID: <f96ba8fa-d587-d35e-2d79-e475e9d0ac65@gentoo.org> (raw)
In-Reply-To: <CAAD4mYjJi1xuORbO4KQh8q+S7WsZ93P9-s+yatvqvqH-n4rPPw@mail.gmail.com>
On 09/22/2017 05:51 PM, R0b0t1 wrote:
> On Thu, Sep 21, 2017 at 2:56 PM, Michał Górny <mgorny@gentoo.org> wrote:
>> [1]:https://wiki.gentoo.org/wiki/Project:Sandbox
>>
>
> I think I understand, in principle, why a sandbox could be useful, but
> would it not be more productive to follow up with projects which do
> unexpected things to ask that they not do those things?
>
The sandbox isn't a security feature, it's more of a QA tool. How do you
*know* when the upstream project does something wrong? See, for example,
https://bugs.gentoo.org/599706
The sandbox doesn't catch something, and the upstream project dropped
DESTDIR from its build system. The result? /usr/bin is now owned by the
"nagios" user. Of course the upstream build system shouldn't be making
/usr/bin owned by nagios, but it would take you a good long time to
notice it without the sandbox.
next prev parent reply other threads:[~2017-09-22 22:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 19:56 [gentoo-dev] Reviving the Sandbox project Michał Górny
2017-09-21 20:33 ` Mart Raudsepp
2017-09-21 20:54 ` Michał Górny
2017-09-21 21:07 ` Mart Raudsepp
2017-09-21 21:25 ` Michał Górny
2017-09-21 22:41 ` Matt Turner
2017-09-22 4:07 ` Michał Górny
2017-09-22 10:57 ` Alexis Ballier
2017-09-22 11:38 ` Sergei Trofimovich
2017-09-22 12:04 ` Alexis Ballier
2017-09-22 12:27 ` Rich Freeman
2017-09-22 15:06 ` James McMechan
2017-09-22 17:03 ` Brian Dolbec
2017-09-22 17:16 ` Patrick McLean
2017-09-22 15:20 ` Michał Górny
2017-09-22 17:15 ` Alexis Ballier
2017-09-22 17:39 ` Michał Górny
2017-09-22 18:31 ` Alexis Ballier
2017-09-22 21:26 ` Michał Górny
2017-09-21 21:28 ` Patrick McLean
2017-09-22 21:51 ` R0b0t1
2017-09-22 22:01 ` Michael Orlitzky [this message]
2017-09-22 22:05 ` Alec Warner
2017-09-23 5:18 ` R0b0t1
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=f96ba8fa-d587-d35e-2d79-e475e9d0ac65@gentoo.org \
--to=mjo@gentoo.org \
--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