[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080922184901.GA3688@us.ibm.com>
Date: Mon, 22 Sep 2008 13:49:01 -0500
From: "Serge E. Hallyn" <serue@...ibm.com>
To: lkml <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org,
James Morris <jmorris@...hat.com>,
Andrew Morgan <morgan@...nel.org>,
Andreas Gruenbacher <agruen@...e.de>,
Andrew Morton <akpm@...l.org>,
Chris Wright <chrisw@...s-sol.org>
Subject: [PATCH 2/2] file capabilities: turn on by default
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@...ibm.com>
Acked-by: Andrew G. Morgan <morgan@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists