2 # Security configuration
5 menu "Security options"
8 bool "Enable access key retention support"
10 This option provides support for retaining authentication tokens and
11 access keys in the kernel.
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.
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,
22 If you are unsure as to whether this is required, answer N.
24 config KEYS_DEBUG_PROC_KEYS
25 bool "Enable the /proc/keys file by which keys may be viewed"
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
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.
37 Only key attributes are listed here; key payloads are not included in
40 If you are unsure as to whether this is required, answer N.
43 bool "Enable different security models"
46 This allows you to choose different security modules to be
47 configured into your kernel.
49 If this option is not selected, the default Linux security
52 If you are unsure how to answer this question, answer N.
55 bool "Enable the securityfs filesystem"
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.
61 If you are unsure how to answer this question, answer N.
63 config SECURITY_NETWORK
64 bool "Socket and Networking Security Hooks"
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.
72 config SECURITY_NETWORK_XFRM
73 bool "XFRM (IPSec) Networking Security Hooks"
74 depends on XFRM && SECURITY_NETWORK
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
83 If you are unsure how to answer this question, answer N.
86 bool "Security hooks for pathname based access control"
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.
94 config SECURITY_FILE_CAPABILITIES
95 bool "File POSIX Capabilities"
98 This enables filesystem capabilities, allowing you to give
99 binaries a subset of root's powers without using setuid 0.
101 If in doubt, answer N.
104 bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
105 depends on HAVE_INTEL_TXT
107 This option enables support for booting the kernel with the
108 Trusted Boot (tboot) module. This will utilize
109 Intel(R) Trusted Execution Technology to perform a measured launch
110 of the kernel. If the system does not support Intel(R) TXT, this
113 Intel TXT will provide higher assurance of system configuration and
114 initial state as well as data reset protection. This is used to
115 create a robust initial kernel measurement and verification, which
116 helps to ensure that kernel security mechanisms are functioning
117 correctly. This level of protection requires a root of trust outside
118 of the kernel itself.
120 Intel TXT also helps solve real end user concerns about having
121 confidence that their hardware is running the VMM or kernel that
122 it was configured with, especially since they may be responsible for
123 providing such assurances to VMs and services running on it.
125 See <http://www.intel.com/technology/security/> for more information
127 See <http://tboot.sourceforge.net> for more information about tboot.
128 See Documentation/intel_txt.txt for a description of how to enable
129 Intel TXT support in a kernel boot.
131 If you are unsure as to whether this is required, answer N.
133 config LSM_MMAP_MIN_ADDR
134 int "Low address space for LSM to protect from user allocation"
135 depends on SECURITY && SECURITY_SELINUX
138 This is the portion of low virtual memory which should be protected
139 from userspace allocation. Keeping a user from writing to low pages
140 can help reduce the impact of kernel NULL pointer bugs.
142 For most ia64, ppc64 and x86 users with lots of address space
143 a value of 65536 is reasonable and should cause no problems.
144 On arm and other archs it should not be higher than 32768.
145 Programs which use vm86 functionality or have some need to map
146 this low address space will need the permission specific to the
149 source security/selinux/Kconfig
150 source security/smack/Kconfig
151 source security/tomoyo/Kconfig
153 source security/integrity/ima/Kconfig
156 prompt "Default security module"
157 default DEFAULT_SECURITY_SELINUX if SECURITY_SELINUX
158 default DEFAULT_SECURITY_SMACK if SECURITY_SMACK
159 default DEFAULT_SECURITY_TOMOYO if SECURITY_TOMOYO
160 default DEFAULT_SECURITY_DAC
163 Select the security module that will be used by default if the
164 kernel parameter security= is not specified.
166 config DEFAULT_SECURITY_SELINUX
167 bool "SELinux" if SECURITY_SELINUX=y
169 config DEFAULT_SECURITY_SMACK
170 bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y
172 config DEFAULT_SECURITY_TOMOYO
173 bool "TOMOYO" if SECURITY_TOMOYO=y
175 config DEFAULT_SECURITY_DAC
176 bool "Unix Discretionary Access Controls"
180 config DEFAULT_SECURITY
182 default "selinux" if DEFAULT_SECURITY_SELINUX
183 default "smack" if DEFAULT_SECURITY_SMACK
184 default "tomoyo" if DEFAULT_SECURITY_TOMOYO
185 default "" if DEFAULT_SECURITY_DAC