Gentoo Archives: gentoo-dev

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

Replies

Subject Author
[gentoo-dev] Re: mbox -- looks sort of interesting Michael Palimaka <kensington@g.o>