Kconfig 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  1. config SECURITY_APPARMOR
  2. bool "AppArmor support"
  3. depends on SECURITY && NET
  4. select AUDIT
  5. select SECURITY_PATH
  6. select SECURITYFS
  7. select SECURITY_NETWORK
  8. default n
  9. help
  10. This enables the AppArmor security module.
  11. Required userspace tools (if they are not included in your
  12. distribution) and further information may be found at
  13. http://apparmor.wiki.kernel.org
  14. If you are unsure how to answer this question, answer N.
  15. config SECURITY_APPARMOR_BOOTPARAM_VALUE
  16. int "AppArmor boot parameter default value"
  17. depends on SECURITY_APPARMOR
  18. range 0 1
  19. default 1
  20. help
  21. This option sets the default value for the kernel parameter
  22. 'apparmor', which allows AppArmor to be enabled or disabled
  23. at boot. If this option is set to 0 (zero), the AppArmor
  24. kernel parameter will default to 0, disabling AppArmor at
  25. boot. If this option is set to 1 (one), the AppArmor
  26. kernel parameter will default to 1, enabling AppArmor at
  27. boot.
  28. If you are unsure how to answer this question, answer 1.
  29. config SECURITY_APPARMOR_HASH
  30. bool "Enable introspection of sha1 hashes for loaded profiles"
  31. depends on SECURITY_APPARMOR
  32. select CRYPTO
  33. select CRYPTO_SHA1
  34. default y
  35. help
  36. This option selects whether introspection of loaded policy
  37. is available to userspace via the apparmor filesystem.
  38. config SECURITY_APPARMOR_HASH_DEFAULT
  39. bool "Enable policy hash introspection by default"
  40. depends on SECURITY_APPARMOR_HASH
  41. default y
  42. help
  43. This option selects whether sha1 hashing of loaded policy
  44. is enabled by default. The generation of sha1 hashes for
  45. loaded policy provide system administrators a quick way
  46. to verify that policy in the kernel matches what is expected,
  47. however it can slow down policy load on some devices. In
  48. these cases policy hashing can be disabled by default and
  49. enabled only if needed.
  50. config SECURITY_APPARMOR_DEBUG
  51. bool "Build AppArmor with debug code"
  52. depends on SECURITY_APPARMOR
  53. default n
  54. help
  55. Build apparmor with debugging logic in apparmor. Not all
  56. debugging logic will necessarily be enabled. A submenu will
  57. provide fine grained control of the debug options that are
  58. available.
  59. config SECURITY_APPARMOR_DEBUG_ASSERTS
  60. bool "Build AppArmor with debugging asserts"
  61. depends on SECURITY_APPARMOR_DEBUG
  62. default y
  63. help
  64. Enable code assertions made with AA_BUG. These are primarily
  65. function entry preconditions but also exist at other key
  66. points. If the assert is triggered it will trigger a WARN
  67. message.
  68. config SECURITY_APPARMOR_DEBUG_MESSAGES
  69. bool "Debug messages enabled by default"
  70. depends on SECURITY_APPARMOR_DEBUG
  71. default n
  72. help
  73. Set the default value of the apparmor.debug kernel parameter.
  74. When enabled, various debug messages will be logged to
  75. the kernel message buffer.