From: "Serge E. Hallyn" <serue@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH -mm] file caps: allow file caps when capabilities are modules
Date: Mon, 19 Feb 2007 11:01:44 -0600 [thread overview]
Message-ID: <20070219170144.GC28412@sergelap.austin.ibm.com> (raw)
From: Serge E. Hallyn <serue@us.ibm.com>
Subject: [PATCH -mm] file caps: allow file caps when capabilities are modules
The security/Kconfig was set up so that file capabilities were
not an option when capabilities were selected as a module. Fix.
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
---
security/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
ea8bfdc0811caad45edf08d95923809c9ed84538
diff --git a/security/Kconfig b/security/Kconfig
index 6d77f68..bc5b1be 100644
--- a/security/Kconfig
+++ b/security/Kconfig
@@ -90,7 +90,7 @@ config SECURITY_CAPABILITIES
config SECURITY_FS_CAPABILITIES
bool "File POSIX Capabilities"
- depends on SECURITY=n || SECURITY_CAPABILITIES=y
+ depends on SECURITY=n || SECURITY_CAPABILITIES!=n
default n
help
This enables filesystem capabilities, allowing you to give
--
1.1.6
reply other threads:[~2007-02-19 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070219170144.GC28412@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®