Blame view
security/Kconfig
6.19 KB
1da177e4c Linux-2.6.12-rc2 |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
# # Security configuration # menu "Security options" config KEYS bool "Enable access key retention support" help This option provides support for retaining authentication tokens and access keys in the kernel. It also includes provision of methods by which such keys might be associated with a process so that network filesystems, encryption support and the like can find them. Furthermore, a special type of key is available that acts as keyring: a searchable sequence of keys. Each process is equipped with access to five standard keyrings: UID-specific, GID-specific, session, process and thread. If you are unsure as to whether this is required, answer N. config KEYS_DEBUG_PROC_KEYS |
06ec7be55 [PATCH] keys: res... |
25 |
bool "Enable the /proc/keys file by which keys may be viewed" |
1da177e4c Linux-2.6.12-rc2 |
26 27 |
depends on KEYS help |
06ec7be55 [PATCH] keys: res... |
28 29 30 |
This option turns on support for the /proc/keys file - through which can be listed all the keys on the system that are viewable by the reading process. |
1da177e4c Linux-2.6.12-rc2 |
31 |
|
06ec7be55 [PATCH] keys: res... |
32 33 34 35 36 37 38 39 40 |
The only keys included in the list are those that grant View permission to the reading process whether or not it possesses them. Note that LSM security checks are still performed, and may further filter out keys that the current process is not authorised to view. Only key attributes are listed here; key payloads are not included in the resulting table. If you are unsure as to whether this is required, answer N. |
1da177e4c Linux-2.6.12-rc2 |
41 42 43 |
config SECURITY bool "Enable different security models" |
2c40579bd [PATCH] SECURITY ... |
44 |
depends on SYSFS |
1da177e4c Linux-2.6.12-rc2 |
45 46 47 48 49 50 51 52 |
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... |
53 54 55 56 |
config SECURITYFS bool "Enable the securityfs filesystem" help This will build the securityfs filesystem. It is currently used by |
3323eec92 integrity: IMA as... |
57 58 |
the TPM bios character driver and IMA, an integrity provider. It is not used by SELinux or SMACK. |
da31894ed securityfs: do no... |
59 60 |
If you are unsure how to answer this question, answer N. |
1da177e4c Linux-2.6.12-rc2 |
61 62 63 64 65 66 67 68 |
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... |
69 70 71 72 73 74 75 76 77 78 79 80 81 |
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 |
82 |
|
be6d3e56a introduce new LSM... |
83 84 85 86 87 88 89 90 |
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... |
91 92 |
config INTEL_TXT bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)" |
69575d388 x86, intel_txt: c... |
93 |
depends on HAVE_INTEL_TXT |
316253406 x86, intel_txt: I... |
94 95 96 97 98 99 |
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... |
100 |
Intel TXT will provide higher assurance of system configuration and |
316253406 x86, intel_txt: I... |
101 102 103 104 105 106 107 108 |
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... |
109 |
it was configured with, especially since they may be responsible for |
316253406 x86, intel_txt: I... |
110 111 112 113 114 115 116 117 118 |
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:... |
119 |
config LSM_MMAP_MIN_ADDR |
024e6cb40 security: Fix pro... |
120 |
int "Low address space for LSM to protect from user allocation" |
788084aba Security/SELinux:... |
121 |
depends on SECURITY && SECURITY_SELINUX |
a58578e47 security: Make LS... |
122 |
default 65536 |
788084aba Security/SELinux:... |
123 124 125 126 127 128 129 130 131 132 133 |
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 |
134 |
source security/selinux/Kconfig |
e114e4737 Smack: Simplified... |
135 |
source security/smack/Kconfig |
00d7d6f84 Kconfig and Makefile |
136 |
source security/tomoyo/Kconfig |
1da177e4c Linux-2.6.12-rc2 |
137 |
|
3323eec92 integrity: IMA as... |
138 |
source security/integrity/ima/Kconfig |
6e65f92ff Config option to ... |
139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 |
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 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 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 default "" if DEFAULT_SECURITY_DAC |
1da177e4c Linux-2.6.12-rc2 |
170 |
endmenu |