From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: fcaps.eclass: bringing filesystem capabilities to the tree
Date: Wed, 30 Jan 2013 01:47:34 +0100 [thread overview]
Message-ID: <51086DA6.5040408@flameeyes.eu> (raw)
In-Reply-To: <pan.2013.01.29.12.14.57@cox.net>
On 29/01/2013 13:14, Duncan wrote:
> For at least reiserfs, and presumably for ext4, since it has
> similar kconfig options, *_FS_XATTR isn't enough,
> *_FS_SECURITY must be enabled as well.
Good point, even I forgot that it's part of security labels rather than
xattr strict (funnily enough, PaX wasn't last time I checked).
> Unfortunately, kernel-help for *_FS_SECURITY implies that it only needs
> to be enabled for SELinux or the like, recommending that it be disabled
> if you're not running such modules. Is it worth filing an upstream
> mainline kernel bug on that as well, suggesting that it mention file-caps
> as well?
Most likely a good idea.
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
prev parent reply other threads:[~2013-01-30 0:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 23:51 [gentoo-dev] fcaps.eclass: bringing filesystem capabilities to the tree Mike Frysinger
2013-01-26 0:10 ` Gilles Dartiguelongue
2013-01-26 0:17 ` Diego Elio Pettenò
2013-01-26 7:46 ` Mike Frysinger
2013-01-26 10:17 ` [gentoo-dev] " Duncan
2013-01-26 16:01 ` [gentoo-dev] " Diego Elio Pettenò
2013-01-26 16:13 ` Rich Freeman
2013-01-26 17:02 ` Diego Elio Pettenò
2013-01-28 19:58 ` Gilles Dartiguelongue
2013-01-26 13:21 ` Michał Górny
2013-01-26 17:08 ` Mike Frysinger
2013-01-26 21:07 ` Doug Goldstein
2013-01-27 17:26 ` Mike Frysinger
2013-01-27 18:24 ` Kacper Kowalik
2013-01-29 12:14 ` [gentoo-dev] " Duncan
2013-01-30 0:47 ` Diego Elio Pettenò [this message]
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=51086DA6.5040408@flameeyes.eu \
--to=flameeyes@flameeyes.eu \
--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