Kconfig 7.9 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
#
# 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.

M
Mimi Zohar 已提交
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
config TRUSTED_KEYS
	tristate "TRUSTED KEYS"
	depends on KEYS && TCG_TPM
	select CRYPTO
	select CRYPTO_HMAC
	select CRYPTO_SHA1
	help
	  This option provides support for creating, sealing, and unsealing
	  keys in the kernel. Trusted keys are random number symmetric keys,
	  generated and RSA-sealed by the TPM. The TPM only unseals the keys,
	  if the boot PCRs and other criteria match.  Userspace will only ever
	  see encrypted blobs.

	  If you are unsure as to whether this is required, answer N.

M
Mimi Zohar 已提交
39 40
config ENCRYPTED_KEYS
	tristate "ENCRYPTED KEYS"
41 42 43
	depends on KEYS
	select CRYPTO
	select CRYPTO_HMAC
M
Mimi Zohar 已提交
44 45 46 47 48 49 50 51 52 53 54 55 56
	select CRYPTO_AES
	select CRYPTO_CBC
	select CRYPTO_SHA256
	select CRYPTO_RNG
	help
	  This option provides support for create/encrypting/decrypting keys
	  in the kernel.  Encrypted keys are kernel generated random numbers,
	  which are encrypted/decrypted with a 'master' symmetric key. The
	  'master' key can be either a trusted-key or user-key type.
	  Userspace only ever sees/stores encrypted blobs.

	  If you are unsure as to whether this is required, answer N.

L
Linus Torvalds 已提交
57
config KEYS_DEBUG_PROC_KEYS
58
	bool "Enable the /proc/keys file by which keys may be viewed"
L
Linus Torvalds 已提交
59 60
	depends on KEYS
	help
61 62 63
	  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.
L
Linus Torvalds 已提交
64

65 66 67 68 69 70 71 72 73
	  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.
L
Linus Torvalds 已提交
74

75 76 77 78 79 80 81 82 83 84 85 86
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.

L
Linus Torvalds 已提交
87 88
config SECURITY
	bool "Enable different security models"
89
	depends on SYSFS
L
Linus Torvalds 已提交
90 91 92 93 94 95 96 97 98
	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.

99 100 101 102
config SECURITYFS
	bool "Enable the securityfs filesystem"
	help
	  This will build the securityfs filesystem.  It is currently used by
103 104
	  the TPM bios character driver and IMA, an integrity provider.  It is
	  not used by SELinux or SMACK.
105 106 107

	  If you are unsure how to answer this question, answer N.

L
Linus Torvalds 已提交
108 109 110 111 112 113 114 115
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.
116 117 118 119 120 121 122 123 124 125 126 127 128

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.
L
Linus Torvalds 已提交
129

130 131 132 133 134 135 136 137 138
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.

139 140
config INTEL_TXT
	bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
141
	depends on HAVE_INTEL_TXT
142 143 144 145 146 147 148
	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.

149
	  Intel TXT will provide higher assurance of system configuration and
150 151 152 153 154 155 156 157
	  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
158
	  it was configured with, especially since they may be responsible for
159 160 161 162 163 164 165 166 167 168
	  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.

169
config LSM_MMAP_MIN_ADDR
170
	int "Low address space for LSM to protect from user allocation"
171
	depends on SECURITY && SECURITY_SELINUX
172
	default 32768 if ARM
173
	default 65536
174 175 176 177 178 179 180 181 182 183 184 185
	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.

L
Linus Torvalds 已提交
186
source security/selinux/Kconfig
187
source security/smack/Kconfig
K
Kentaro Takeda 已提交
188
source security/tomoyo/Kconfig
189
source security/apparmor/Kconfig
L
Linus Torvalds 已提交
190

191
source security/integrity/Kconfig
192

J
John Johansen 已提交
193 194 195 196 197
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
198
	default DEFAULT_SECURITY_APPARMOR if SECURITY_APPARMOR
J
John Johansen 已提交
199 200 201 202 203 204 205 206 207 208 209 210 211 212 213
	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

214 215 216
	config DEFAULT_SECURITY_APPARMOR
		bool "AppArmor" if SECURITY_APPARMOR=y

J
John Johansen 已提交
217 218 219 220 221 222 223 224 225 226
	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
227
	default "apparmor" if DEFAULT_SECURITY_APPARMOR
J
John Johansen 已提交
228 229
	default "" if DEFAULT_SECURITY_DAC

L
Linus Torvalds 已提交
230 231
endmenu