Blame view
security/Kconfig
5.72 KB
1da177e4c Linux-2.6.12-rc2 |
1 2 3 4 5 |
# # Security configuration # menu "Security options" |
f0894940a KEYS: Move the ke... |
6 |
source security/keys/Kconfig |
1da177e4c Linux-2.6.12-rc2 |
7 |
|
eaf06b241 Restrict unprivil... |
8 9 10 11 12 13 14 15 16 17 18 |
config SECURITY_DMESG_RESTRICT bool "Restrict unprivileged access to the kernel syslog" default n help This enforces restrictions on unprivileged users reading the kernel syslog via dmesg(8). If this option is not selected, no restrictions will be enforced unless the dmesg_restrict sysctl is explicitly set to (1). If you are unsure how to answer this question, answer N. |
1da177e4c Linux-2.6.12-rc2 |
19 20 |
config SECURITY bool "Enable different security models" |
2c40579bd [PATCH] SECURITY ... |
21 |
depends on SYSFS |
2813893f8 kernel: condition... |
22 |
depends on MULTIUSER |
1da177e4c Linux-2.6.12-rc2 |
23 24 25 26 27 28 29 30 |
help This allows you to choose different security modules to be configured into your kernel. If this option is not selected, the default Linux security model will be used. If you are unsure how to answer this question, answer N. |
da31894ed securityfs: do no... |
31 32 33 34 |
config SECURITYFS bool "Enable the securityfs filesystem" help This will build the securityfs filesystem. It is currently used by |
3323eec92 integrity: IMA as... |
35 36 |
the TPM bios character driver and IMA, an integrity provider. It is not used by SELinux or SMACK. |
da31894ed securityfs: do no... |
37 38 |
If you are unsure how to answer this question, answer N. |
1da177e4c Linux-2.6.12-rc2 |
39 40 41 42 43 44 45 46 |
config SECURITY_NETWORK bool "Socket and Networking Security Hooks" depends on SECURITY help This enables the socket and networking security hooks. If enabled, a security module can use these hooks to implement socket and networking access controls. If you are unsure how to answer this question, answer N. |
df71837d5 [LSM-IPSec]: Secu... |
47 48 49 50 51 52 53 54 55 56 57 58 59 |
config SECURITY_NETWORK_XFRM bool "XFRM (IPSec) Networking Security Hooks" depends on XFRM && SECURITY_NETWORK help This enables the XFRM (IPSec) networking security hooks. If enabled, a security module can use these hooks to implement per-packet access controls based on labels derived from IPSec policy. Non-IPSec communications are designated as unlabelled, and only sockets authorized to communicate unlabelled data can send without using IPSec. If you are unsure how to answer this question, answer N. |
1da177e4c Linux-2.6.12-rc2 |
60 |
|
be6d3e56a introduce new LSM... |
61 62 63 64 65 66 67 68 |
config SECURITY_PATH bool "Security hooks for pathname based access control" depends on SECURITY help This enables the security hooks for pathname based access control. If enabled, a security module can use these hooks to implement pathname based access controls. If you are unsure how to answer this question, answer N. |
316253406 x86, intel_txt: I... |
69 70 |
config INTEL_TXT bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)" |
69575d388 x86, intel_txt: c... |
71 |
depends on HAVE_INTEL_TXT |
316253406 x86, intel_txt: I... |
72 73 74 75 76 77 |
help This option enables support for booting the kernel with the Trusted Boot (tboot) module. This will utilize Intel(R) Trusted Execution Technology to perform a measured launch of the kernel. If the system does not support Intel(R) TXT, this will have no effect. |
3c556e419 x86, intel_txt: F... |
78 |
Intel TXT will provide higher assurance of system configuration and |
316253406 x86, intel_txt: I... |
79 80 81 82 83 84 85 86 |
initial state as well as data reset protection. This is used to create a robust initial kernel measurement and verification, which helps to ensure that kernel security mechanisms are functioning correctly. This level of protection requires a root of trust outside of the kernel itself. Intel TXT also helps solve real end user concerns about having confidence that their hardware is running the VMM or kernel that |
3c556e419 x86, intel_txt: F... |
87 |
it was configured with, especially since they may be responsible for |
316253406 x86, intel_txt: I... |
88 89 90 91 92 93 94 95 96 |
providing such assurances to VMs and services running on it. See <http://www.intel.com/technology/security/> for more information about Intel(R) TXT. See <http://tboot.sourceforge.net> for more information about tboot. See Documentation/intel_txt.txt for a description of how to enable Intel TXT support in a kernel boot. If you are unsure as to whether this is required, answer N. |
788084aba Security/SELinux:... |
97 |
config LSM_MMAP_MIN_ADDR |
024e6cb40 security: Fix pro... |
98 |
int "Low address space for LSM to protect from user allocation" |
788084aba Security/SELinux:... |
99 |
depends on SECURITY && SECURITY_SELINUX |
530b099df security: select ... |
100 |
default 32768 if ARM || (ARM64 && COMPAT) |
a58578e47 security: Make LS... |
101 |
default 65536 |
788084aba Security/SELinux:... |
102 103 104 105 106 107 108 109 110 111 112 |
help This is the portion of low virtual memory which should be protected from userspace allocation. Keeping a user from writing to low pages can help reduce the impact of kernel NULL pointer bugs. For most ia64, ppc64 and x86 users with lots of address space a value of 65536 is reasonable and should cause no problems. On arm and other archs it should not be higher than 32768. Programs which use vm86 functionality or have some need to map this low address space will need the permission specific to the systems running LSM. |
1da177e4c Linux-2.6.12-rc2 |
113 |
source security/selinux/Kconfig |
e114e4737 Smack: Simplified... |
114 |
source security/smack/Kconfig |
00d7d6f84 Kconfig and Makefile |
115 |
source security/tomoyo/Kconfig |
f9ad1af53 AppArmor: Enable ... |
116 |
source security/apparmor/Kconfig |
2d514487f security: Yama LSM |
117 |
source security/yama/Kconfig |
1da177e4c Linux-2.6.12-rc2 |
118 |
|
f381c2722 integrity: move i... |
119 |
source security/integrity/Kconfig |
3323eec92 integrity: IMA as... |
120 |
|
6e65f92ff Config option to ... |
121 122 123 124 125 |
choice prompt "Default security module" default DEFAULT_SECURITY_SELINUX if SECURITY_SELINUX default DEFAULT_SECURITY_SMACK if SECURITY_SMACK default DEFAULT_SECURITY_TOMOYO if SECURITY_TOMOYO |
f9ad1af53 AppArmor: Enable ... |
126 |
default DEFAULT_SECURITY_APPARMOR if SECURITY_APPARMOR |
2d514487f security: Yama LSM |
127 |
default DEFAULT_SECURITY_YAMA if SECURITY_YAMA |
6e65f92ff Config option to ... |
128 129 130 131 132 133 134 135 136 137 138 139 140 141 |
default DEFAULT_SECURITY_DAC help Select the security module that will be used by default if the kernel parameter security= is not specified. config DEFAULT_SECURITY_SELINUX bool "SELinux" if SECURITY_SELINUX=y config DEFAULT_SECURITY_SMACK bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y config DEFAULT_SECURITY_TOMOYO bool "TOMOYO" if SECURITY_TOMOYO=y |
f9ad1af53 AppArmor: Enable ... |
142 143 |
config DEFAULT_SECURITY_APPARMOR bool "AppArmor" if SECURITY_APPARMOR=y |
2d514487f security: Yama LSM |
144 145 |
config DEFAULT_SECURITY_YAMA bool "Yama" if SECURITY_YAMA=y |
6e65f92ff Config option to ... |
146 147 148 149 150 151 152 153 154 155 |
config DEFAULT_SECURITY_DAC bool "Unix Discretionary Access Controls" endchoice config DEFAULT_SECURITY string default "selinux" if DEFAULT_SECURITY_SELINUX default "smack" if DEFAULT_SECURITY_SMACK default "tomoyo" if DEFAULT_SECURITY_TOMOYO |
f9ad1af53 AppArmor: Enable ... |
156 |
default "apparmor" if DEFAULT_SECURITY_APPARMOR |
2d514487f security: Yama LSM |
157 |
default "yama" if DEFAULT_SECURITY_YAMA |
6e65f92ff Config option to ... |
158 |
default "" if DEFAULT_SECURITY_DAC |
1da177e4c Linux-2.6.12-rc2 |
159 |
endmenu |