From: "Andrew G. Morgan" <morgan@kernel.org>
To: Serge Hallyn <serue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com, agruen@suse.de
Subject: Re: [PATCH 2/2] file capabilities: turn on by default
Date: Thu, 28 Aug 2008 17:37:02 -0700 [thread overview]
Message-ID: <48B744AE.5040606@kernel.org> (raw)
In-Reply-To: <fe7784a0710a8fef0ac2e4f39589dff6f8293ad0.1219951973.git.serue@us.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Acked-by: Andrew G. Morgan <morgan@kernel.org>
Cheers
Andrew
Serge Hallyn wrote:
| 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>
| ---
| 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"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIt0Sp+bHCR3gb8jsRAmQuAKDXiLp/7hZ++JDxv1rL1kIVqS/YtgCeJIMk
zmPFh8NjFrUnElWyeF5R/Jo=
=AK55
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-08-29 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 19:54 [PATCH 1/2] file capabilities: add no_file_caps switch (v2) 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 [this message]
2008-08-29 0:35 ` [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Andrew G. Morgan
-- strict thread matches above, loose matches on Subject: below --
2008-09-22 18:48 Serge E. Hallyn
2008-09-22 18:49 ` [PATCH 2/2] file capabilities: turn on by default Serge E. Hallyn
2008-09-22 19:03 ` Randy Dunlap
2008-09-22 19:56 ` Serge E. Hallyn
2008-09-22 21:09 ` Randy Dunlap
2008-09-22 22:53 ` Chris Wright
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=48B744AE.5040606@kernel.org \
--to=morgan@kernel.org \
--cc=agruen@suse.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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