From: "Serge E. Hallyn" <serue@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
James Morris <jmorris@redhat.com>,
Andrew Morgan <morgan@kernel.org>,
Andreas Gruenbacher <agruen@suse.de>,
Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>
Subject: [PATCH 2/2] file capabilities: turn on by default
Date: Mon, 22 Sep 2008 13:49:01 -0500 [thread overview]
Message-ID: <20080922184901.GA3688@us.ibm.com> (raw)
In-Reply-To: <20080922184835.GA2826@us.ibm.com>
Now that file capabilities can be turned off at boot, go ahead
and compile them into the kernel by default by making
CONFIG_SECURITY_FILE_CAPABILITIES=y the default.
Note that the boot flag no_file_caps must be specified to turn
file capabilities off, as by default they are on. So the
default behavior is in fact changed.
Signed-off-by: Serge Hallyn <serue@us.ibm.com>
Acked-by: Andrew G. Morgan <morgan@kernel.org>
---
security/Kconfig | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/security/Kconfig b/security/Kconfig
index 5592939..6fbb233 100644
--- a/security/Kconfig
+++ b/security/Kconfig
@@ -75,12 +75,15 @@ config SECURITY_NETWORK_XFRM
config SECURITY_FILE_CAPABILITIES
bool "File POSIX Capabilities"
- default n
+ default y
help
This enables filesystem capabilities, allowing you to give
binaries a subset of root's powers without using setuid 0.
- If in doubt, answer N.
+ You can still boot with the no_file_caps option to disable
+ file capabilities.
+
+ If in doubt, answer Y.
config SECURITY_ROOTPLUG
bool "Root Plug Support"
--
1.5.4.3
next prev parent reply other threads:[~2008-09-22 18:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 18:48 [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Serge E. Hallyn
2008-09-22 18:49 ` Serge E. Hallyn [this message]
2008-09-22 19:03 ` [PATCH 2/2] file capabilities: turn on by default Randy Dunlap
2008-09-22 19:56 ` Serge E. Hallyn
2008-09-22 21:09 ` Randy Dunlap
2008-09-22 22:53 ` Chris Wright
2008-09-22 19:16 ` [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Stephen Smalley
2008-09-22 20:09 ` Andreas Gruenbacher
2008-09-22 21:50 ` Serge E. Hallyn
2008-09-22 22:08 ` Andreas Gruenbacher
2008-09-23 6:48 ` James Morris
2008-09-22 22:57 ` Chris Wright
2008-09-23 15:51 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 19:54 Serge Hallyn
2008-08-28 19:54 ` [PATCH 2/2] file capabilities: turn on by default Serge Hallyn
2008-08-29 0:37 ` Andrew G. Morgan
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=20080922184901.GA3688@us.ibm.com \
--to=serue@us.ibm.com \
--cc=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 \
/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