public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Hjalmarsson <xake@rymdraket.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: [RFC] Enable userpriv by default? Support RESTRICT=userpriv? Interaction with prefix in EAPI 3?
Date: Fri, 11 Dec 2009 23:46:07 +0100	[thread overview]
Message-ID: <1260571567.12483.0.camel@lillen.dodi> (raw)
In-Reply-To: <4B22A759.1090509@gentoo.org>

fre 2009-12-11 klockan 12:11 -0800 skrev Zac Medico:
> Should we enable FEATURES=userpriv by default? If we do that then do
> we also need to support RESTRICT=userpriv? Maybe RESTRICT=userpriv
> should not be supported on the grounds that it is never justified?
> What about prefix support (in EAPI 3), which often doesn't have root
> privileges?

That would be problematic for hardened, as they set the permission
for /usr/src/* to root only.





  parent reply	other threads:[~2009-12-12  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 20:11 [gentoo-dev] [RFC] Enable userpriv by default? Support RESTRICT=userpriv? Interaction with prefix in EAPI 3? Zac Medico
2009-12-11 21:58 ` justin
2009-12-11 22:06   ` Zac Medico
2009-12-12  1:31     ` Justin Lecher
2009-12-11 22:46 ` Peter Hjalmarsson [this message]
2009-12-12  1:03   ` [gentoo-dev] " Duncan

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=1260571567.12483.0.camel@lillen.dodi \
    --to=xake@rymdraket.net \
    --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