On Thu, 11 Jan 2007 11:56:09 -0500 Mike Frysinger <[EMAIL PROTECTED]> wrote: | On Wednesday 10 January 2007 20:01, Ciaran McCreesh wrote: | > On Wed, 10 Jan 2007 19:56:00 -0500 Mike Frysinger | > <[EMAIL PROTECTED]> | > | as stated in original e-mail, unattended/sandbox are just some | > | examples, not the only ones | > | > So which RESTRICT values *should* the user legitimately have to care | > about? | | On Wednesday 10 January 2007 16:40, Chris Gianelloni wrote: | > I am a user. I don't want any of my compiles executing with | > elevated privileges. I have FEATURES=userpriv. Package foo has | > RESTRICT=userpriv. I don't have ACCEPT_RESTRICT=userpriv. When I | > try to install package foo, it fails, because I don't want to allow | > RESTRICT=userpriv.
Bogus argument. If an ebuild were truly doing something naughty with elevated privs, it could just do it in one of the pkg_ phases. Since userpriv isn't a security feature, there's no advantage for the end user in restricting based upon it. So again, which RESTRICT variables should the user legitimately have to care about? -- Ciaran McCreesh Mail : ciaranm at ciaranm.org Web : http://ciaranm.org/ Paludis, the secure package manager : http://paludis.pioto.org/
signature.asc
Description: PGP signature
