From: Andreas Gruenbacher <agruen@suse.de>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
James Morris <jmorris@redhat.com>,
Andrew Morgan <morgan@kernel.org>, Andrew Morton <akpm@osdl.org>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH 2/2] file capabilities: remove CONFIG_SECURITY_FILE_CAPABILITIES
Date: Thu, 25 Sep 2008 03:36:27 +0200 [thread overview]
Message-ID: <200809250336.27647.agruen@suse.de> (raw)
In-Reply-To: <20080925010233.GB7324@us.ibm.com>
On Thursday, 25 September 2008 3:02:33 Serge E. Hallyn wrote:
> Quoting Chris Wright (chrisw@sous-sol.org):
> > What is being done to enable userspace in distros to make those 570
> > bytes generally useful?
>
> Fedora 9 and ubuntu intrepid already have full capabilities support and
> modern libcap. Sles is set to ship with a modern libcap, and according
> to what Andreas is saying, if we can provide them with the no_file_caps
> boot option then suse is willing to have a kernel with capabilities
> turned on.
Yes.
> I think gentoo still comes with libcap-1. Need to look into
> changing that.
>
> I suppose the next baby-step will be to do get rid of setuid on little
> things like ping.
Real file capability support in RPM seems important to me; hacking this
into %post scripts is not a reasonable approach.
Thanks,
Andreas
prev parent reply other threads:[~2008-09-25 1:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 2:04 [PATCH 1/2] file capabilities: add no_file_caps switch (v3) Serge E. Hallyn
2008-09-24 2:05 ` [PATCH 2/2] file capabilities: remove CONFIG_SECURITY_FILE_CAPABILITIES Serge E. Hallyn
2008-09-24 4:59 ` Andrew G. Morgan
2008-09-24 23:49 ` Chris Wright
2008-09-25 1:02 ` Serge E. Hallyn
2008-09-25 1:19 ` Chris Wright
2008-09-25 1:36 ` Andreas Gruenbacher [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=200809250336.27647.agruen@suse.de \
--to=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=serue@us.ibm.com \
/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