summaryrefslogtreecommitdiffstats
path: root/security/yama/Kconfig
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2012-09-04 13:32:13 -0700
committerJames Morris <james.l.morris@oracle.com>2012-09-05 14:12:31 -0700
commitc6993e4ac002c92bc75379212e9179c36d4bf7ee (patch)
treecdb4c800ea3cf4003b07087166cc767dab79032f /security/yama/Kconfig
parent81198078d7da4240f3cbfc2c6a8ea6cd417f51a7 (diff)
downloadop-kernel-dev-c6993e4ac002c92bc75379212e9179c36d4bf7ee.zip
op-kernel-dev-c6993e4ac002c92bc75379212e9179c36d4bf7ee.tar.gz
security: allow Yama to be unconditionally stacked
Unconditionally call Yama when CONFIG_SECURITY_YAMA_STACKED is selected, no matter what LSM module is primary. Ubuntu and Chrome OS already carry patches to do this, and Fedora has voiced interest in doing this as well. Instead of having multiple distributions (or LSM authors) carrying these patches, just allow Yama to be called unconditionally when selected by the new CONFIG. Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: Serge E. Hallyn <serge.hallyn@canonical.com> Acked-by: Eric Paris <eparis@redhat.com> Acked-by: John Johansen <john.johansen@canonical.com> Signed-off-by: James Morris <james.l.morris@oracle.com>
Diffstat (limited to 'security/yama/Kconfig')
-rw-r--r--security/yama/Kconfig8
1 files changed, 8 insertions, 0 deletions
diff --git a/security/yama/Kconfig b/security/yama/Kconfig
index 51d6709..20ef514 100644
--- a/security/yama/Kconfig
+++ b/security/yama/Kconfig
@@ -11,3 +11,11 @@ config SECURITY_YAMA
Further information can be found in Documentation/security/Yama.txt.
If you are unsure how to answer this question, answer N.
+
+config SECURITY_YAMA_STACKED
+ bool "Yama stacked with other LSMs"
+ depends on SECURITY_YAMA
+ default n
+ help
+ When Yama is built into the kernel, force it to stack with the
+ selected primary LSM.
OpenPOWER on IntegriCloud