|author||Kees Cook <firstname.lastname@example.org>||2015-07-23 18:02:48 -0700|
|committer||James Morris <email@example.com>||2015-07-28 13:18:19 +1000|
|parent||Merge tag 'seccomp-next' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux into next (diff)|
Yama: remove needless CONFIG_SECURITY_YAMA_STACKED
Now that minor LSMs can cleanly stack with major LSMs, remove the unneeded config for Yama to be made to explicitly stack. Just selecting the main Yama CONFIG will allow it to work, regardless of the major LSM. Since distros using Yama are already forcing it to stack, this is effectively a no-op change. Additionally add MAINTAINERS entry. Signed-off-by: Kees Cook <firstname.lastname@example.org> Signed-off-by: James Morris <email@example.com>
Diffstat (limited to 'security/yama/Kconfig')
1 files changed, 1 insertions, 8 deletions
diff --git a/security/yama/Kconfig b/security/yama/Kconfig
index 3123e1da2fed..90c605eea892 100644
@@ -6,14 +6,7 @@ config SECURITY_YAMA
This selects Yama, which extends DAC support with additional
system-wide security settings beyond regular Linux discretionary
access controls. Currently available is ptrace scope restriction.
+ Like capabilities, this security module stacks with other LSMs.
Further information can be found in Documentation/security/Yama.txt.
If you are unsure how to answer this question, answer N.
- bool "Yama stacked with other LSMs"
- depends on SECURITY_YAMA
- default n
- When Yama is built into the kernel, force it to stack with the
- selected primary LSM.