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