2010-07-30 10:46:33 +07:00
|
|
|
config SECURITY_APPARMOR
|
|
|
|
bool "AppArmor support"
|
2010-08-03 00:52:18 +07:00
|
|
|
depends on SECURITY && NET
|
2010-07-30 10:46:33 +07:00
|
|
|
select AUDIT
|
|
|
|
select SECURITY_PATH
|
|
|
|
select SECURITYFS
|
|
|
|
select SECURITY_NETWORK
|
|
|
|
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 SECURITY_APPARMOR_BOOTPARAM_VALUE
|
|
|
|
int "AppArmor boot parameter default value"
|
|
|
|
depends on SECURITY_APPARMOR
|
|
|
|
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.
|
2013-08-15 01:27:36 +07:00
|
|
|
|
|
|
|
config SECURITY_APPARMOR_HASH
|
|
|
|
bool "SHA1 hash of loaded profiles"
|
|
|
|
depends on SECURITY_APPARMOR
|
2015-10-22 02:16:29 +07:00
|
|
|
select CRYPTO
|
2013-08-15 01:27:36 +07:00
|
|
|
select CRYPTO_SHA1
|
|
|
|
default y
|
|
|
|
|
|
|
|
help
|
|
|
|
This option selects whether sha1 hashing is done against loaded
|
|
|
|
profiles and exported for inspection to user space via the apparmor
|
|
|
|
filesystem.
|