Root/
1 | # |
2 | # Security configuration |
3 | # |
4 | |
5 | menu "Security options" |
6 | |
7 | config KEYS |
8 | bool "Enable access key retention support" |
9 | help |
10 | This option provides support for retaining authentication tokens and |
11 | access keys in the kernel. |
12 | |
13 | It also includes provision of methods by which such keys might be |
14 | associated with a process so that network filesystems, encryption |
15 | support and the like can find them. |
16 | |
17 | Furthermore, a special type of key is available that acts as keyring: |
18 | a searchable sequence of keys. Each process is equipped with access |
19 | to five standard keyrings: UID-specific, GID-specific, session, |
20 | process and thread. |
21 | |
22 | If you are unsure as to whether this is required, answer N. |
23 | |
24 | config KEYS_DEBUG_PROC_KEYS |
25 | bool "Enable the /proc/keys file by which keys may be viewed" |
26 | depends on KEYS |
27 | help |
28 | This option turns on support for the /proc/keys file - through which |
29 | can be listed all the keys on the system that are viewable by the |
30 | reading process. |
31 | |
32 | The only keys included in the list are those that grant View |
33 | permission to the reading process whether or not it possesses them. |
34 | Note that LSM security checks are still performed, and may further |
35 | filter out keys that the current process is not authorised to view. |
36 | |
37 | Only key attributes are listed here; key payloads are not included in |
38 | the resulting table. |
39 | |
40 | If you are unsure as to whether this is required, answer N. |
41 | |
42 | config SECURITY |
43 | bool "Enable different security models" |
44 | depends on SYSFS |
45 | help |
46 | This allows you to choose different security modules to be |
47 | configured into your kernel. |
48 | |
49 | If this option is not selected, the default Linux security |
50 | model will be used. |
51 | |
52 | If you are unsure how to answer this question, answer N. |
53 | |
54 | config SECURITYFS |
55 | bool "Enable the securityfs filesystem" |
56 | help |
57 | This will build the securityfs filesystem. It is currently used by |
58 | the TPM bios character driver and IMA, an integrity provider. It is |
59 | not used by SELinux or SMACK. |
60 | |
61 | If you are unsure how to answer this question, answer N. |
62 | |
63 | config SECURITY_NETWORK |
64 | bool "Socket and Networking Security Hooks" |
65 | depends on SECURITY |
66 | help |
67 | This enables the socket and networking security hooks. |
68 | If enabled, a security module can use these hooks to |
69 | implement socket and networking access controls. |
70 | If you are unsure how to answer this question, answer N. |
71 | |
72 | config SECURITY_NETWORK_XFRM |
73 | bool "XFRM (IPSec) Networking Security Hooks" |
74 | depends on XFRM && SECURITY_NETWORK |
75 | help |
76 | This enables the XFRM (IPSec) networking security hooks. |
77 | If enabled, a security module can use these hooks to |
78 | implement per-packet access controls based on labels |
79 | derived from IPSec policy. Non-IPSec communications are |
80 | designated as unlabelled, and only sockets authorized |
81 | to communicate unlabelled data can send without using |
82 | IPSec. |
83 | If you are unsure how to answer this question, answer N. |
84 | |
85 | config SECURITY_PATH |
86 | bool "Security hooks for pathname based access control" |
87 | depends on SECURITY |
88 | help |
89 | This enables the security hooks for pathname based access control. |
90 | If enabled, a security module can use these hooks to |
91 | implement pathname based access controls. |
92 | If you are unsure how to answer this question, answer N. |
93 | |
94 | config INTEL_TXT |
95 | bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)" |
96 | depends on HAVE_INTEL_TXT |
97 | help |
98 | This option enables support for booting the kernel with the |
99 | Trusted Boot (tboot) module. This will utilize |
100 | Intel(R) Trusted Execution Technology to perform a measured launch |
101 | of the kernel. If the system does not support Intel(R) TXT, this |
102 | will have no effect. |
103 | |
104 | Intel TXT will provide higher assurance of system configuration and |
105 | initial state as well as data reset protection. This is used to |
106 | create a robust initial kernel measurement and verification, which |
107 | helps to ensure that kernel security mechanisms are functioning |
108 | correctly. This level of protection requires a root of trust outside |
109 | of the kernel itself. |
110 | |
111 | Intel TXT also helps solve real end user concerns about having |
112 | confidence that their hardware is running the VMM or kernel that |
113 | it was configured with, especially since they may be responsible for |
114 | providing such assurances to VMs and services running on it. |
115 | |
116 | See <http://www.intel.com/technology/security/> for more information |
117 | about Intel(R) TXT. |
118 | See <http://tboot.sourceforge.net> for more information about tboot. |
119 | See Documentation/intel_txt.txt for a description of how to enable |
120 | Intel TXT support in a kernel boot. |
121 | |
122 | If you are unsure as to whether this is required, answer N. |
123 | |
124 | config LSM_MMAP_MIN_ADDR |
125 | int "Low address space for LSM to protect from user allocation" |
126 | depends on SECURITY && SECURITY_SELINUX |
127 | default 65536 |
128 | help |
129 | This is the portion of low virtual memory which should be protected |
130 | from userspace allocation. Keeping a user from writing to low pages |
131 | can help reduce the impact of kernel NULL pointer bugs. |
132 | |
133 | For most ia64, ppc64 and x86 users with lots of address space |
134 | a value of 65536 is reasonable and should cause no problems. |
135 | On arm and other archs it should not be higher than 32768. |
136 | Programs which use vm86 functionality or have some need to map |
137 | this low address space will need the permission specific to the |
138 | systems running LSM. |
139 | |
140 | source security/selinux/Kconfig |
141 | source security/smack/Kconfig |
142 | source security/tomoyo/Kconfig |
143 | |
144 | source security/integrity/ima/Kconfig |
145 | |
146 | choice |
147 | prompt "Default security module" |
148 | default DEFAULT_SECURITY_SELINUX if SECURITY_SELINUX |
149 | default DEFAULT_SECURITY_SMACK if SECURITY_SMACK |
150 | default DEFAULT_SECURITY_TOMOYO if SECURITY_TOMOYO |
151 | default DEFAULT_SECURITY_DAC |
152 | |
153 | help |
154 | Select the security module that will be used by default if the |
155 | kernel parameter security= is not specified. |
156 | |
157 | config DEFAULT_SECURITY_SELINUX |
158 | bool "SELinux" if SECURITY_SELINUX=y |
159 | |
160 | config DEFAULT_SECURITY_SMACK |
161 | bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y |
162 | |
163 | config DEFAULT_SECURITY_TOMOYO |
164 | bool "TOMOYO" if SECURITY_TOMOYO=y |
165 | |
166 | config DEFAULT_SECURITY_DAC |
167 | bool "Unix Discretionary Access Controls" |
168 | |
169 | endchoice |
170 | |
171 | config DEFAULT_SECURITY |
172 | string |
173 | default "selinux" if DEFAULT_SECURITY_SELINUX |
174 | default "smack" if DEFAULT_SECURITY_SMACK |
175 | default "tomoyo" if DEFAULT_SECURITY_TOMOYO |
176 | default "" if DEFAULT_SECURITY_DAC |
177 | |
178 | endmenu |
179 | |
180 |
Branches:
ben-wpan
ben-wpan-stefan
javiroman/ks7010
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.11
jz-3.12
jz-3.13
jz-3.15
jz-3.16
jz-3.18-dt
jz-3.2
jz-3.3
jz-3.4
jz-3.5
jz-3.6
jz-3.6-rc2-pwm
jz-3.9
jz-3.9-clk
jz-3.9-rc8
jz47xx
jz47xx-2.6.38
master
Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7
v3.9