Kconfig 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config SECURITY_TOMOYO
  3. bool "TOMOYO Linux Support"
  4. depends on SECURITY
  5. depends on NET
  6. select SECURITYFS
  7. select SECURITY_PATH
  8. select SECURITY_NETWORK
  9. select SRCU
  10. select BUILD_BIN2C
  11. default n
  12. help
  13. This selects TOMOYO Linux, pathname-based access control.
  14. Required userspace tools and further information may be
  15. found at <http://tomoyo.sourceforge.jp/>.
  16. If you are unsure how to answer this question, answer N.
  17. config SECURITY_TOMOYO_MAX_ACCEPT_ENTRY
  18. int "Default maximal count for learning mode"
  19. default 2048
  20. range 0 2147483647
  21. depends on SECURITY_TOMOYO
  22. help
  23. This is the default value for maximal ACL entries
  24. that are automatically appended into policy at "learning mode".
  25. Some programs access thousands of objects, so running
  26. such programs in "learning mode" dulls the system response
  27. and consumes much memory.
  28. This is the safeguard for such programs.
  29. config SECURITY_TOMOYO_MAX_AUDIT_LOG
  30. int "Default maximal count for audit log"
  31. default 1024
  32. range 0 2147483647
  33. depends on SECURITY_TOMOYO
  34. help
  35. This is the default value for maximal entries for
  36. audit logs that the kernel can hold on memory.
  37. You can read the log via /sys/kernel/security/tomoyo/audit.
  38. If you don't need audit logs, you may set this value to 0.
  39. config SECURITY_TOMOYO_OMIT_USERSPACE_LOADER
  40. bool "Activate without calling userspace policy loader."
  41. default n
  42. depends on SECURITY_TOMOYO
  43. help
  44. Say Y here if you want to activate access control as soon as built-in
  45. policy was loaded. This option will be useful for systems where
  46. operations which can lead to the hijacking of the boot sequence are
  47. needed before loading the policy. For example, you can activate
  48. immediately after loading the fixed part of policy which will allow
  49. only operations needed for mounting a partition which contains the
  50. variant part of policy and verifying (e.g. running GPG check) and
  51. loading the variant part of policy. Since you can start using
  52. enforcing mode from the beginning, you can reduce the possibility of
  53. hijacking the boot sequence.
  54. config SECURITY_TOMOYO_POLICY_LOADER
  55. string "Location of userspace policy loader"
  56. default "/sbin/tomoyo-init"
  57. depends on SECURITY_TOMOYO
  58. depends on !SECURITY_TOMOYO_OMIT_USERSPACE_LOADER
  59. help
  60. This is the default pathname of policy loader which is called before
  61. activation. You can override this setting via TOMOYO_loader= kernel
  62. command line option.
  63. config SECURITY_TOMOYO_ACTIVATION_TRIGGER
  64. string "Trigger for calling userspace policy loader"
  65. default "/sbin/init"
  66. depends on SECURITY_TOMOYO
  67. depends on !SECURITY_TOMOYO_OMIT_USERSPACE_LOADER
  68. help
  69. This is the default pathname of activation trigger.
  70. You can override this setting via TOMOYO_trigger= kernel command line
  71. option. For example, if you pass init=/bin/systemd option, you may
  72. want to also pass TOMOYO_trigger=/bin/systemd option.
  73. config SECURITY_TOMOYO_INSECURE_BUILTIN_SETTING
  74. bool "Use insecure built-in settings for fuzzing tests."
  75. default n
  76. depends on SECURITY_TOMOYO
  77. select SECURITY_TOMOYO_OMIT_USERSPACE_LOADER
  78. help
  79. Enabling this option forces minimal built-in policy and disables
  80. domain/program checks for run-time policy modifications. Please enable
  81. this option only if this kernel is built for doing fuzzing tests.