From: Maxim Kammerer <mk@dee.su>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Enable FEATURES="userpriv usersandbox" by default?
Date: Tue, 29 May 2012 04:09:12 +0300 [thread overview]
Message-ID: <CAHsXYDAW7o24Mmk9qWaoem-SD-ddff0otAJWxk3jZBUgCz0NLw@mail.gmail.com> (raw)
In-Reply-To: <4FC3EF5E.90900@gentoo.org>
On Tue, May 29, 2012 at 12:34 AM, Zac Medico <zmedico@gentoo.org> wrote:
> Note that ebuilds can set RESTRICT="userpriv" if they require superuser
> privileges during any of the src_* phases that userpriv affects.
Current list of packages in portage using userpriv restriction:
app-laptop/tp_smapi
dev-db/firebird
games-board/gnuchess-book
games-fps/quakeforge
games-rpg/wastesedge
gnome-extra/gnome-lirc-properties
mail-filter/qmail-scanner (vpopmail)
media-gfx/gtkimageview
media-gfx/imagemagick (when USE=perl)
net-dialup/ltmodem
net-libs/courier-authlib (vpopmail)
net-mail/courier-imap (vpopmail)
net-mail/qmailadmin (vpopmail)
net-mail/vpopmail (old stable)
net-misc/icaclient
sys-fs/udev (when USE=test for udev-9999 only)
It could also be that anything vpopmail-related doesn't need
RESTRICT=userpriv anymore.
> I've been using FEATURES="userpriv usersandbox" for years, and I don't
> remember experiencing any problems because of it, so I think that it
> would be reasonable to have it enabled by default.
Ditto, ~2 years with regular full @world rebuild.
--
Maxim Kammerer
Liberté Linux: http://dee.su/liberte
next prev parent reply other threads:[~2012-05-29 1:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 21:34 [gentoo-dev] RFC: Enable FEATURES="userpriv usersandbox" by default? Zac Medico
2012-05-28 21:46 ` Andreas K. Huettel
2012-05-28 21:52 ` Davide Pesavento
2012-05-28 23:17 ` Michael Weber
2012-05-28 23:56 ` [gentoo-dev] " Duncan
2012-05-29 1:09 ` Maxim Kammerer [this message]
2012-05-29 1:58 ` [gentoo-dev] " Rich Freeman
2012-05-29 8:43 ` Agostino Sarubbo
2012-05-29 8:58 ` Richard Yao
2012-05-29 9:05 ` Zac Medico
2012-05-29 14:11 ` Michał Górny
2012-05-29 14:50 ` Rich Freeman
2012-05-29 14:57 ` hasufell
2012-05-29 15:23 ` Rich Freeman
2012-05-29 16:27 ` hasufell
2012-05-29 17:08 ` Jeff Horelick
2012-05-29 19:46 ` Michael Orlitzky
2012-05-29 19:58 ` Mike Gilbert
2012-05-29 20:21 ` Michael Orlitzky
2012-05-29 20:05 ` William Hubbs
2012-05-29 21:47 ` Hilco Wijbenga
2012-05-29 22:11 ` Zac Medico
2012-05-29 23:22 ` Richard Yao
2012-05-30 0:38 ` Zac Medico
2012-05-30 0:59 ` Hilco Wijbenga
2012-05-29 19:44 ` Ralph Sennhauser
2012-05-29 22:09 ` Zac Medico
2012-05-29 20:32 ` Zac Medico
2012-07-02 19:48 ` Pacho Ramos
2012-07-02 20:01 ` Zac Medico
2012-07-02 20:36 ` vivo75
2012-07-02 20:45 ` Zac Medico
2012-07-03 7:18 ` Pacho Ramos
2012-07-03 8:02 ` Michał Górny
2013-07-21 10:53 ` Pacho Ramos
2013-07-21 18:25 ` Zac Medico
2013-07-21 18:30 ` Alex Xu
2013-07-21 18:35 ` Mike Gilbert
2012-07-03 8:11 ` vivo75
2012-07-03 13:50 ` Andreas K. Huettel
2012-07-03 13:55 ` Andreas K. Huettel
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=CAHsXYDAW7o24Mmk9qWaoem-SD-ddff0otAJWxk3jZBUgCz0NLw@mail.gmail.com \
--to=mk@dee.su \
--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