blob: bd72ae6234947e424885f3808dbec54bddad244c [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Security configuration
3#
4
5menu "Security options"
6
7config 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
24config KEYS_DEBUG_PROC_KEYS
Michael LeMay06ec7be2006-06-26 00:24:56 -070025 bool "Enable the /proc/keys file by which keys may be viewed"
Linus Torvalds1da177e2005-04-16 15:20:36 -070026 depends on KEYS
27 help
Michael LeMay06ec7be2006-06-26 00:24:56 -070028 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.
Linus Torvalds1da177e2005-04-16 15:20:36 -070031
Michael LeMay06ec7be2006-06-26 00:24:56 -070032 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.
Linus Torvalds1da177e2005-04-16 15:20:36 -070041
42config SECURITY
43 bool "Enable different security models"
Adrian Bunk2c405792005-08-22 18:20:50 +020044 depends on SYSFS
Linus Torvalds1da177e2005-04-16 15:20:36 -070045 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
Eric Parisda318942008-08-22 11:35:57 -040054config SECURITYFS
55 bool "Enable the securityfs filesystem"
56 help
57 This will build the securityfs filesystem. It is currently used by
Mimi Zohar3323eec2009-02-04 09:06:58 -050058 the TPM bios character driver and IMA, an integrity provider. It is
59 not used by SELinux or SMACK.
Eric Parisda318942008-08-22 11:35:57 -040060
61 If you are unsure how to answer this question, answer N.
62
Linus Torvalds1da177e2005-04-16 15:20:36 -070063config 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
Trent Jaegerdf718372005-12-13 23:12:27 -080072config 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
Kentaro Takedabe6d3e52008-12-17 13:24:15 +090085config 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
Joseph Cihula31625342009-06-30 19:30:59 -070094config INTEL_TXT
95 bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
Shane Wang69575d32009-09-01 18:25:07 -070096 depends on HAVE_INTEL_TXT
Joseph Cihula31625342009-06-30 19:30:59 -070097 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
Arnaldo Carvalho de Melo3c556e42009-08-12 12:00:40 -0300104 Intel TXT will provide higher assurance of system configuration and
Joseph Cihula31625342009-06-30 19:30:59 -0700105 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
Arnaldo Carvalho de Melo3c556e42009-08-12 12:00:40 -0300113 it was configured with, especially since they may be responsible for
Joseph Cihula31625342009-06-30 19:30:59 -0700114 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
Eric Paris788084a2009-07-31 12:54:11 -0400124config LSM_MMAP_MIN_ADDR
Andreas Schwab024e6cb2009-08-18 22:14:29 +0200125 int "Low address space for LSM to protect from user allocation"
Eric Paris788084a2009-07-31 12:54:11 -0400126 depends on SECURITY && SECURITY_SELINUX
Dave Jonesa58578e2009-08-18 13:47:37 -0400127 default 65536
Eric Paris788084a2009-07-31 12:54:11 -0400128 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700140source security/selinux/Kconfig
Casey Schauflere114e472008-02-04 22:29:50 -0800141source security/smack/Kconfig
Kentaro Takeda00d7d6f2009-02-05 17:18:17 +0900142source security/tomoyo/Kconfig
John Johansenf9ad1af2010-07-29 14:48:08 -0700143source security/apparmor/Kconfig
Linus Torvalds1da177e2005-04-16 15:20:36 -0700144
Mimi Zohar3323eec2009-02-04 09:06:58 -0500145source security/integrity/ima/Kconfig
146
John Johansen6e65f922009-11-05 17:03:20 -0800147choice
148 prompt "Default security module"
149 default DEFAULT_SECURITY_SELINUX if SECURITY_SELINUX
150 default DEFAULT_SECURITY_SMACK if SECURITY_SMACK
151 default DEFAULT_SECURITY_TOMOYO if SECURITY_TOMOYO
John Johansenf9ad1af2010-07-29 14:48:08 -0700152 default DEFAULT_SECURITY_APPARMOR if SECURITY_APPARMOR
John Johansen6e65f922009-11-05 17:03:20 -0800153 default DEFAULT_SECURITY_DAC
154
155 help
156 Select the security module that will be used by default if the
157 kernel parameter security= is not specified.
158
159 config DEFAULT_SECURITY_SELINUX
160 bool "SELinux" if SECURITY_SELINUX=y
161
162 config DEFAULT_SECURITY_SMACK
163 bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y
164
165 config DEFAULT_SECURITY_TOMOYO
166 bool "TOMOYO" if SECURITY_TOMOYO=y
167
John Johansenf9ad1af2010-07-29 14:48:08 -0700168 config DEFAULT_SECURITY_APPARMOR
169 bool "AppArmor" if SECURITY_APPARMOR=y
170
John Johansen6e65f922009-11-05 17:03:20 -0800171 config DEFAULT_SECURITY_DAC
172 bool "Unix Discretionary Access Controls"
173
174endchoice
175
176config DEFAULT_SECURITY
177 string
178 default "selinux" if DEFAULT_SECURITY_SELINUX
179 default "smack" if DEFAULT_SECURITY_SMACK
180 default "tomoyo" if DEFAULT_SECURITY_TOMOYO
John Johansenf9ad1af2010-07-29 14:48:08 -0700181 default "apparmor" if DEFAULT_SECURITY_APPARMOR
John Johansen6e65f922009-11-05 17:03:20 -0800182 default "" if DEFAULT_SECURITY_DAC
183
Linus Torvalds1da177e2005-04-16 15:20:36 -0700184endmenu
185