summaryrefslogtreecommitdiffstats
path: root/security/Kconfig
diff options
context:
space:
mode:
authorPetr Vorel <pvorel@suse.cz>2019-02-28 18:54:48 -0500
committerJames Morris <james.morris@microsoft.com>2019-03-01 12:52:54 -0500
commitb102c11e1a10e1328c9610665e45dd07bf4a3696 (patch)
tree1965b2529cf125b3bba38ed4631d1331b02d7c2c /security/Kconfig
parent89a9684ea158dd7eef1728be9f0aed9a7d41cf19 (diff)
LSM: Update list of SECURITYFS users in Kconfig
Remove modules not using it (SELinux and SMACK aren't the only ones not using it). Signed-off-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: James Morris <james.morris@microsoft.com>
Diffstat (limited to 'security/Kconfig')
-rw-r--r--security/Kconfig3
1 files changed, 1 insertions, 2 deletions
diff --git a/security/Kconfig b/security/Kconfig
index 9555f4914492..1d6463fb1450 100644
--- a/security/Kconfig
+++ b/security/Kconfig
@@ -40,8 +40,7 @@ config SECURITYFS
40 bool "Enable the securityfs filesystem" 40 bool "Enable the securityfs filesystem"
41 help 41 help
42 This will build the securityfs filesystem. It is currently used by 42 This will build the securityfs filesystem. It is currently used by
43 the TPM bios character driver and IMA, an integrity provider. It is 43 various security modules (AppArmor, IMA, SafeSetID, TOMOYO, TPM).
44 not used by SELinux or SMACK.
45 44
46 If you are unsure how to answer this question, answer N. 45 If you are unsure how to answer this question, answer N.
47 46