summaryrefslogtreecommitdiff
path: root/security/Kconfig
diff options
context:
space:
mode:
authorPetr Vorel <pvorel@suse.cz>2019-03-01 00:54:48 +0100
committerJames Morris <james.morris@microsoft.com>2019-03-01 09:52:54 -0800
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
bool "Enable the securityfs filesystem"
help
This will build the securityfs filesystem. It is currently used by
- the TPM bios character driver and IMA, an integrity provider. It is
- not used by SELinux or SMACK.
+ various security modules (AppArmor, IMA, SafeSetID, TOMOYO, TPM).
If you are unsure how to answer this question, answer N.