PageRenderTime 90ms CodeModel.GetById 20ms RepoModel.GetById 0ms app.codeStats 1ms

#! | 179 lines | 143 code | 36 blank | 0 comment | 0 complexity | 7bba73f3109cb6e3d6cc3a63ac23043e MD5 | raw file
Possible License(s): CC-BY-SA-3.0, GPL-2.0, LGPL-2.0, AGPL-1.0
  1. #
  2. # Security configuration
  3. #
  4. menu "Security options"
  5. config KEYS
  6. bool "Enable access key retention support"
  7. help
  8. This option provides support for retaining authentication tokens and
  9. access keys in the kernel.
  10. It also includes provision of methods by which such keys might be
  11. associated with a process so that network filesystems, encryption
  12. support and the like can find them.
  13. Furthermore, a special type of key is available that acts as keyring:
  14. a searchable sequence of keys. Each process is equipped with access
  15. to five standard keyrings: UID-specific, GID-specific, session,
  16. process and thread.
  17. If you are unsure as to whether this is required, answer N.
  19. bool "Enable the /proc/keys file by which keys may be viewed"
  20. depends on KEYS
  21. help
  22. This option turns on support for the /proc/keys file - through which
  23. can be listed all the keys on the system that are viewable by the
  24. reading process.
  25. The only keys included in the list are those that grant View
  26. permission to the reading process whether or not it possesses them.
  27. Note that LSM security checks are still performed, and may further
  28. filter out keys that the current process is not authorised to view.
  29. Only key attributes are listed here; key payloads are not included in
  30. the resulting table.
  31. If you are unsure as to whether this is required, answer N.
  32. config SECURITY
  33. bool "Enable different security models"
  34. depends on SYSFS
  35. help
  36. This allows you to choose different security modules to be
  37. configured into your kernel.
  38. If this option is not selected, the default Linux security
  39. model will be used.
  40. If you are unsure how to answer this question, answer N.
  41. config SECURITYFS
  42. bool "Enable the securityfs filesystem"
  43. help
  44. This will build the securityfs filesystem. It is currently used by
  45. the TPM bios character driver and IMA, an integrity provider. It is
  46. not used by SELinux or SMACK.
  47. If you are unsure how to answer this question, answer N.
  49. bool "Socket and Networking Security Hooks"
  50. depends on SECURITY
  51. help
  52. This enables the socket and networking security hooks.
  53. If enabled, a security module can use these hooks to
  54. implement socket and networking access controls.
  55. If you are unsure how to answer this question, answer N.
  57. bool "XFRM (IPSec) Networking Security Hooks"
  58. depends on XFRM && SECURITY_NETWORK
  59. help
  60. This enables the XFRM (IPSec) networking security hooks.
  61. If enabled, a security module can use these hooks to
  62. implement per-packet access controls based on labels
  63. derived from IPSec policy. Non-IPSec communications are
  64. designated as unlabelled, and only sockets authorized
  65. to communicate unlabelled data can send without using
  66. IPSec.
  67. If you are unsure how to answer this question, answer N.
  68. config SECURITY_PATH
  69. bool "Security hooks for pathname based access control"
  70. depends on SECURITY
  71. help
  72. This enables the security hooks for pathname based access control.
  73. If enabled, a security module can use these hooks to
  74. implement pathname based access controls.
  75. If you are unsure how to answer this question, answer N.
  76. config INTEL_TXT
  77. bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
  78. depends on HAVE_INTEL_TXT
  79. help
  80. This option enables support for booting the kernel with the
  81. Trusted Boot (tboot) module. This will utilize
  82. Intel(R) Trusted Execution Technology to perform a measured launch
  83. of the kernel. If the system does not support Intel(R) TXT, this
  84. will have no effect.
  85. Intel TXT will provide higher assurance of system configuration and
  86. initial state as well as data reset protection. This is used to
  87. create a robust initial kernel measurement and verification, which
  88. helps to ensure that kernel security mechanisms are functioning
  89. correctly. This level of protection requires a root of trust outside
  90. of the kernel itself.
  91. Intel TXT also helps solve real end user concerns about having
  92. confidence that their hardware is running the VMM or kernel that
  93. it was configured with, especially since they may be responsible for
  94. providing such assurances to VMs and services running on it.
  95. See <> for more information
  96. about Intel(R) TXT.
  97. See <> for more information about tboot.
  98. See Documentation/intel_txt.txt for a description of how to enable
  99. Intel TXT support in a kernel boot.
  100. If you are unsure as to whether this is required, answer N.
  101. config LSM_MMAP_MIN_ADDR
  102. int "Low address space for LSM to protect from user allocation"
  103. depends on SECURITY && SECURITY_SELINUX
  104. default 65536
  105. help
  106. This is the portion of low virtual memory which should be protected
  107. from userspace allocation. Keeping a user from writing to low pages
  108. can help reduce the impact of kernel NULL pointer bugs.
  109. For most ia64, ppc64 and x86 users with lots of address space
  110. a value of 65536 is reasonable and should cause no problems.
  111. On arm and other archs it should not be higher than 32768.
  112. Programs which use vm86 functionality or have some need to map
  113. this low address space will need the permission specific to the
  114. systems running LSM.
  115. source security/selinux/Kconfig
  116. source security/smack/Kconfig
  117. source security/tomoyo/Kconfig
  118. source security/integrity/ima/Kconfig
  119. choice
  120. prompt "Default security module"
  125. help
  126. Select the security module that will be used by default if the
  127. kernel parameter security= is not specified.
  129. bool "SELinux" if SECURITY_SELINUX=y
  131. bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y
  133. bool "TOMOYO" if SECURITY_TOMOYO=y
  135. bool "Unix Discretionary Access Controls"
  136. endchoice
  137. config DEFAULT_SECURITY
  138. string
  139. default "selinux" if DEFAULT_SECURITY_SELINUX
  140. default "smack" if DEFAULT_SECURITY_SMACK
  141. default "tomoyo" if DEFAULT_SECURITY_TOMOYO
  142. default "" if DEFAULT_SECURITY_DAC
  143. endmenu