config [31mCONFIG_SECURITY_APPARMOR[0m bool "AppArmor support" depends on [31mCONFIG_SECURITY[0m && [31mCONFIG_NET[0m select [31mCONFIG_AUDIT[0m select [31mCONFIG_SECURITY_PATH[0m select [31mCONFIG_SECURITYFS[0m select [31mCONFIG_SECURITY_NETWORK[0m default n help This enables the AppArmor security module. Required userspace tools (if they are not included in your distribution) and further information may be found at http://apparmor.wiki.kernel.org If you are unsure how to answer this question, answer N. config [31mCONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE[0m int "AppArmor boot parameter default value" depends on [31mCONFIG_SECURITY_APPARMOR[0m range 0 1 default 1 help This option sets the default value for the kernel parameter 'apparmor', which allows AppArmor to be enabled or disabled at boot. If this option is set to 0 (zero), the AppArmor kernel parameter will default to 0, disabling AppArmor at boot. If this option is set to 1 (one), the AppArmor kernel parameter will default to 1, enabling AppArmor at boot. If you are unsure how to answer this question, answer 1. config [31mCONFIG_SECURITY_APPARMOR_HASH[0m bool "Enable introspection of sha1 hashes for loaded profiles" depends on [31mCONFIG_SECURITY_APPARMOR[0m select [31mCONFIG_CRYPTO[0m select [31mCONFIG_CRYPTO_SHA1[0m default y help This option selects whether introspection of loaded policy is available to userspace via the apparmor filesystem. config [31mCONFIG_SECURITY_APPARMOR_HASH_DEFAULT[0m bool "Enable policy hash introspection by default" depends on [31mCONFIG_SECURITY_APPARMOR_HASH[0m default y help This option selects whether sha1 hashing of loaded policy is enabled by default. The generation of sha1 hashes for loaded policy provide system administrators a quick way to verify that policy in the kernel matches what is expected, however it can slow down policy load on some devices. In these cases policy hashing can be disabled by default and enabled only if needed. |