From: mortonm@chromium.org
To: rdunlap@infradead.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Cc: Micah Morton <mortonm@chromium.org>
Subject: [PATCH] LSM: SafeSetID: 'depend' on CONFIG_SECURITY
Date: Tue, 29 Jan 2019 10:54:24 -0800 [thread overview]
Message-ID: <20190129185424.251139-1-mortonm@chromium.org> (raw)
In-Reply-To: <CAJ-EccMgDvx81g-XgWymdYn_G5Ou8mgbef3GUbx-C_Ai5qF-pQ@mail.gmail.com>
From: Micah Morton <mortonm@chromium.org>
This patch changes the Kconfig file for the SafeSetID LSM to depend on
CONFIG_SECURITY as well as select CONFIG_SECURITYFS, since the policies
for the LSM are configured through writing to securityfs.
Signed-off-by: Micah Morton <mortonm@chromium.org>
---
security/safesetid/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/security/safesetid/Kconfig b/security/safesetid/Kconfig
index bf89a47ffcc8..4f415c4e3f93 100644
--- a/security/safesetid/Kconfig
+++ b/security/safesetid/Kconfig
@@ -1,5 +1,7 @@
config SECURITY_SAFESETID
bool "Gate setid transitions to limit CAP_SET{U/G}ID capabilities"
+ depends on SECURITY
+ select SECURITYFS
default n
help
SafeSetID is an LSM module that gates the setid family of syscalls to
--
2.20.1.495.gaa96b0ce6b-goog
next prev parent reply other threads:[~2019-01-29 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 6:11 linux-next: Tree for Jan 29 Stephen Rothwell
2019-01-29 16:30 ` linux-next: Tree for Jan 29 (net/ipv4/devinet.c) Randy Dunlap
2019-01-29 16:50 ` linux-next: Tree for Jan 29 (SLIMbus & SND_SOC_WCD9335) Randy Dunlap
2019-01-29 16:57 ` Srinivas Kandagatla
2019-01-29 17:00 ` Randy Dunlap
2019-01-29 17:04 ` linux-next: Tree for Jan 29 (security/safesetid/) Randy Dunlap
2019-01-29 18:21 ` Micah Morton
2019-01-29 18:54 ` mortonm [this message]
2019-01-29 19:52 ` [PATCH] LSM: SafeSetID: 'depend' on CONFIG_SECURITY James Morris
2019-01-29 17:17 ` linux-next: Tree for Jan 29 (security/integrity/) Randy Dunlap
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=20190129185424.251139-1-mortonm@chromium.org \
--to=mortonm@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).