Gentoo Archives: gentoo-dev

From: Michael Palimaka <kensington@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: mbox -- looks sort of interesting
Date: Wed, 12 Feb 2014 11:46:34
Message-Id: ldfmt4$ah7$1@ger.gmane.org
In Reply to: Re: [gentoo-dev] Re: mbox -- looks sort of interesting by Brian Dolbec
1 On 02/12/2014 04:56 PM, Brian Dolbec wrote:
2 > On Wed, 12 Feb 2014 01:36:01 +1100
3 > Michael Palimaka <kensington@g.o> wrote:
4 >
5 >> On 02/12/2014 01:03 AM, Rich Freeman wrote:
6 >>> On Tue, Feb 11, 2014 at 7:39 AM, Michael Palimaka
7 >>> <kensington@g.o> wrote:
8 >>>> On 02/11/2014 11:34 PM, Rich Freeman wrote:
9 >>>>
10 >>>>> One of those ideas I've always wanted to implement is to create a
11 >>>>> portage hook/patch that looks at the dependencies for the package
12 >>>>> being built and configures sandbox to block read-access to
13 >>>>> anything that wasn't explicitly declared. Sandbox works for
14 >>>>> read-access as well as write-access, though
15 >>>>> in /etc/sandbox.d/00default read-access is enabled everywhere by
16 >>>>> default.
17 >>>>>
18 >>>>> And, yes, it could be configured to allow access to @system...
19 >>>> That's pretty much what emerge_strict does.
20 >>>
21 >>> What is emerge_strict? The Google is failing me here...
22 >>>
23 >>> Rich
24 >>>
25 >>>
26 >> Sorry, I should have clarified. It's provided by autodep, extending
27 >> the dependency analysis by denying access to any files not part of the
28 >> specified dependencies and @system.
29 >>
30 >>
31 >
32 > There was a gentoo gsoc project a few years ago that did exactly this
33 > for doing dep checks on ebuilds. There was also one for determining
34 > deps automatically.
35 >
36 > Is this the project mentioned? ^^^
37 >
38
39 Should be, autodep was GSoC 2011.

Replies

Subject Author
Re: [gentoo-dev] Re: mbox -- looks sort of interesting "Александр Берсенев" <bay@×××××××××.ru>