From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: blueness@gentoo.org
Subject: Re: [gentoo-dev] POSIX capability in Gentoo
Date: Tue, 2 Aug 2011 09:08:32 +0200 [thread overview]
Message-ID: <20110802090832.2cd03a32@pomiocik.lan> (raw)
In-Reply-To: <4E35B468.10604@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
On Sun, 31 Jul 2011 16:00:40 -0400
"Anthony G. Basile" <blueness@gentoo.org> wrote:
> On 07/31/2011 03:46 PM, Nirbheek Chauhan wrote:
> > On Sun, Jul 31, 2011 at 8:13 PM, Anthony G. Basile
> > <blueness@gentoo.org> wrote:
> >> Hi everyone,
> >>
> >> A couple of days ago, bonsaikitten (Patrick), kerframil (Kerin
> >> Millar) and myself were talking about other distros moving away
> >> from setuid binaries towards caps. Openwall and Fedora are now
> >> setuid-less [1]. Some googling showed that Constanze has done
> >> quite a bit of work in the area and that there was a consensus to
> >> include functions to set caps within portage [2]. I don't know
> >> what, if anything has been done since then, but I'd like to lend
> >> my support.
> >>
> > One problem that came up was that a lot of people use tmpfs for
> > /var/tmp/portage, and tmpfs doesn't support xattrs which are needed
> > for setting caps.
> >
> > Linux 3.0 has added support for xattrs with tmpfs (the redhat folks
> > did the work, afaik), so that problem is partly solved now.
>
> I know, there are lots of places where xattrs is not supported that
> lead to the same problem. I'm tempted to respond with pkg_postinst()
> but I see QA problems written all over that.
We can either do that or 'Future EAPI' capsetting in PMS. Then, a PM
could implement capsetting functions in a such way that they will
preserve caps internally to PM and re-set them when merging to livefs.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2011-08-02 7:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 14:43 [gentoo-dev] POSIX capability in Gentoo Anthony G. Basile
2011-07-31 19:46 ` Nirbheek Chauhan
2011-07-31 20:00 ` Anthony G. Basile
2011-08-02 7:08 ` Michał Górny [this message]
2011-08-02 14:28 ` Anthony G. Basile
2011-08-02 14:31 ` Ciaran McCreesh
2011-08-02 14:51 ` Anthony G. Basile
2011-08-02 14:54 ` Ciaran McCreesh
2011-08-02 15:05 ` Anthony G. Basile
2011-08-02 15:05 ` Ciaran McCreesh
2011-08-02 15:19 ` Anthony G. Basile
2011-08-02 15:20 ` Ciaran McCreesh
2011-08-02 17:11 ` [gentoo-dev] " Duncan
2011-08-02 17:17 ` Ciaran McCreesh
2011-08-02 17:36 ` Jonathan Callen
[not found] ` <20110802173846.AF04F21C12C@pigeon.gentoo.org>
2011-08-02 17:39 ` Ciaran McCreesh
2011-08-02 20:46 ` Arfrever Frehtes Taifersar Arahesis
2011-08-03 1:19 ` Duncan
2011-08-03 0:29 ` Brian Harring
2011-08-03 11:34 ` Ciaran McCreesh
2011-08-03 21:26 ` Brian Harring
2011-08-03 21:28 ` Ciaran McCreesh
2011-08-03 21:52 ` Brian Harring
2011-08-02 15:15 ` [gentoo-dev] " Rich Freeman
2011-08-02 15:09 ` Michał Górny
2011-07-31 20:28 ` Michał Górny
2011-07-31 20:27 ` Ciaran McCreesh
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=20110802090832.2cd03a32@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=blueness@gentoo.org \
--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