Kconfig 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
  1. config SECURITY_SELINUX
  2. bool "NSA SELinux Support"
  3. depends on SECURITY_NETWORK && AUDIT && NET && INET
  4. select NETWORK_SECMARK
  5. default n
  6. help
  7. This selects NSA Security-Enhanced Linux (SELinux).
  8. You will also need a policy configuration and a labeled filesystem.
  9. If you are unsure how to answer this question, answer N.
  10. config SECURITY_SELINUX_BOOTPARAM
  11. bool "NSA SELinux boot parameter"
  12. depends on SECURITY_SELINUX
  13. default n
  14. help
  15. This option adds a kernel parameter 'selinux', which allows SELinux
  16. to be disabled at boot. If this option is selected, SELinux
  17. functionality can be disabled with selinux=0 on the kernel
  18. command line. The purpose of this option is to allow a single
  19. kernel image to be distributed with SELinux built in, but not
  20. necessarily enabled.
  21. If you are unsure how to answer this question, answer N.
  22. config SECURITY_SELINUX_BOOTPARAM_VALUE
  23. int "NSA SELinux boot parameter default value"
  24. depends on SECURITY_SELINUX_BOOTPARAM
  25. range 0 1
  26. default 1
  27. help
  28. This option sets the default value for the kernel parameter
  29. 'selinux', which allows SELinux to be disabled at boot. If this
  30. option is set to 0 (zero), the SELinux kernel parameter will
  31. default to 0, disabling SELinux at bootup. If this option is
  32. set to 1 (one), the SELinux kernel parameter will default to 1,
  33. enabling SELinux at bootup.
  34. If you are unsure how to answer this question, answer 1.
  35. config SECURITY_SELINUX_DISABLE
  36. bool "NSA SELinux runtime disable"
  37. depends on SECURITY_SELINUX
  38. default n
  39. help
  40. This option enables writing to a selinuxfs node 'disable', which
  41. allows SELinux to be disabled at runtime prior to the policy load.
  42. SELinux will then remain disabled until the next boot.
  43. This option is similar to the selinux=0 boot parameter, but is to
  44. support runtime disabling of SELinux, e.g. from /sbin/init, for
  45. portability across platforms where boot parameters are difficult
  46. to employ.
  47. If you are unsure how to answer this question, answer N.
  48. config SECURITY_SELINUX_DEVELOP
  49. bool "NSA SELinux Development Support"
  50. depends on SECURITY_SELINUX
  51. default y
  52. help
  53. This enables the development support option of NSA SELinux,
  54. which is useful for experimenting with SELinux and developing
  55. policies. If unsure, say Y. With this option enabled, the
  56. kernel will start in permissive mode (log everything, deny nothing)
  57. unless you specify enforcing=1 on the kernel command line. You
  58. can interactively toggle the kernel between enforcing mode and
  59. permissive mode (if permitted by the policy) via /selinux/enforce.
  60. config SECURITY_SELINUX_AVC_STATS
  61. bool "NSA SELinux AVC Statistics"
  62. depends on SECURITY_SELINUX
  63. default y
  64. help
  65. This option collects access vector cache statistics to
  66. /selinux/avc/cache_stats, which may be monitored via
  67. tools such as avcstat.
  68. config SECURITY_SELINUX_CHECKREQPROT_VALUE
  69. int "NSA SELinux checkreqprot default value"
  70. depends on SECURITY_SELINUX
  71. range 0 1
  72. default 0
  73. help
  74. This option sets the default value for the 'checkreqprot' flag
  75. that determines whether SELinux checks the protection requested
  76. by the application or the protection that will be applied by the
  77. kernel (including any implied execute for read-implies-exec) for
  78. mmap and mprotect calls. If this option is set to 0 (zero),
  79. SELinux will default to checking the protection that will be applied
  80. by the kernel. If this option is set to 1 (one), SELinux will
  81. default to checking the protection requested by the application.
  82. The checkreqprot flag may be changed from the default via the
  83. 'checkreqprot=' boot parameter. It may also be changed at runtime
  84. via /selinux/checkreqprot if authorized by policy.
  85. If you are unsure how to answer this question, answer 0.
  86. config SECURITY_SELINUX_POLICYDB_VERSION_MAX
  87. bool "NSA SELinux maximum supported policy format version"
  88. depends on SECURITY_SELINUX
  89. default n
  90. help
  91. This option enables the maximum policy format version supported
  92. by SELinux to be set to a particular value. This value is reported
  93. to userspace via /selinux/policyvers and used at policy load time.
  94. It can be adjusted downward to support legacy userland (init) that
  95. does not correctly handle kernels that support newer policy versions.
  96. Examples:
  97. For the Fedora Core 3 or 4 Linux distributions, enable this option
  98. and set the value via the next option. For Fedora Core 5 and later,
  99. do not enable this option.
  100. If you are unsure how to answer this question, answer N.
  101. config SECURITY_SELINUX_POLICYDB_VERSION_MAX_VALUE
  102. int "NSA SELinux maximum supported policy format version value"
  103. depends on SECURITY_SELINUX_POLICYDB_VERSION_MAX
  104. range 15 23
  105. default 19
  106. help
  107. This option sets the value for the maximum policy format version
  108. supported by SELinux.
  109. Examples:
  110. For Fedora Core 3, use 18.
  111. For Fedora Core 4, use 19.
  112. If you are unsure how to answer this question, look for the
  113. policy format version supported by your policy toolchain, by
  114. running 'checkpolicy -V'. Or look at what policy you have
  115. installed under /etc/selinux/$SELINUXTYPE/policy, where
  116. SELINUXTYPE is defined in your /etc/selinux/config.