From: "Serge E. Hallyn" <serue@us.ibm.com>
To: "Andrew G. Morgan" <morgan@kernel.org>
Cc: Andreas Gruenbacher <agruen@suse.de>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [patch] file capabilities: Add no_file_caps switch
Date: Thu, 28 Aug 2008 12:09:38 -0500 [thread overview]
Message-ID: <20080828170938.GA13286@us.ibm.com> (raw)
In-Reply-To: <48B6C5B1.1050109@kernel.org>
Quoting Andrew G. Morgan (morgan@kernel.org):
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sorry to get to this late.
>
> I very much prefer this patch over the resuscitation of the cap_set_pg()
> code.
>
> [I would also like to advocate we combine it with making
> CONFIG_SECURITY_FILE_CAPABILITIES=y the default config option.]
I certainly don't mind that, but I would expect complaints about this
unless the default boot option were 'n'.
Do you think it's worth sending as a separate trivial patch? Then if
people object to one both changes won't be held up.
(Anyway that's what I'll do right now)
-serge
next prev parent reply other threads:[~2008-08-28 17:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 18:57 [patch] file capabilities: Add no_file_caps switch Andreas Gruenbacher
2008-08-26 20:28 ` Ingo Molnar
2008-08-27 13:52 ` Serge E. Hallyn
2008-08-27 15:29 ` Andreas Gruenbacher
2008-08-27 16:04 ` Serge E. Hallyn
2008-08-27 16:13 ` David Howells
2008-08-27 16:32 ` Alan Cox
2008-08-27 17:00 ` David Howells
2008-08-27 16:57 ` Andreas Gruenbacher
2008-08-27 17:04 ` David Howells
2008-08-27 18:58 ` Serge E. Hallyn
2008-08-27 21:14 ` David Howells
2008-08-28 0:05 ` James Morris
2008-08-28 0:48 ` Serge E. Hallyn
2008-08-28 1:57 ` James Morris
2008-08-28 15:35 ` Andrew G. Morgan
2008-08-28 17:09 ` Serge E. Hallyn [this message]
2008-08-28 16:27 ` Andreas Gruenbacher
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=20080828170938.GA13286@us.ibm.com \
--to=serue@us.ibm.com \
--cc=agruen@suse.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@kernel.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