[net-next-2.6.git] / security / Kconfig

#
# 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
	bool "Enable the /proc/keys file by which keys may be viewed"
	depends on KEYS
	help
	  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.

	  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.

config SECURITY
	bool "Enable different security models"
	depends on SYSFS
	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.

config SECURITYFS
	bool "Enable the securityfs filesystem"
	help
	  This will build the securityfs filesystem.  It is currently used by
	  the TPM bios character driver and IMA, an integrity provider.  It is
	  not used by SELinux or SMACK.

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

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.

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.

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.

config INTEL_TXT
	bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
	depends on HAVE_INTEL_TXT
	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.

	  Intel TXT will provide higher assurance of system configuration and
	  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
	  it was configured with, especially since they may be responsible for
	  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.

config LSM_MMAP_MIN_ADDR
	int "Low address space for LSM to protect from user allocation"
	depends on SECURITY && SECURITY_SELINUX
	default 65536
	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.

source security/selinux/Kconfig
source security/smack/Kconfig
source security/tomoyo/Kconfig
source security/apparmor/Kconfig

source security/integrity/ima/Kconfig

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_APPARMOR if SECURITY_APPARMOR
	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_APPARMOR
		bool "AppArmor" if SECURITY_APPARMOR=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 "apparmor" if DEFAULT_SECURITY_APPARMOR
	default "" if DEFAULT_SECURITY_DAC

endmenu
Commit	Line	Data
1da177e4 LT	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
06ec7be5	25	bool "Enable the /proc/keys file by which keys may be viewed"
1da177e4 LT	26	depends on KEYS
1da177e4 LT	27	help
06ec7be5 ML	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.
1da177e4	31
06ec7be5 ML	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.
1da177e4 LT	41
	42	config SECURITY
	43	bool "Enable different security models"
2c40579b	44	depends on SYSFS
1da177e4 LT	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
da31894e EP	54	config SECURITYFS
	55	bool "Enable the securityfs filesystem"
	56	help
	57	This will build the securityfs filesystem. It is currently used by
3323eec9 MZ	58	the TPM bios character driver and IMA, an integrity provider. It is
3323eec9 MZ	59	not used by SELinux or SMACK.
da31894e EP	60
	61	If you are unsure how to answer this question, answer N.
	62
1da177e4 LT	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.
df71837d TJ	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.
1da177e4	84
be6d3e56 KT	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
31625340 JC	94	config INTEL_TXT
31625340 JC	95	bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
69575d38	96	depends on HAVE_INTEL_TXT
31625340 JC	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
3c556e41	104	Intel TXT will provide higher assurance of system configuration and
31625340 JC	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
3c556e41	113	it was configured with, especially since they may be responsible for
31625340 JC	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
788084ab	124	config LSM_MMAP_MIN_ADDR
024e6cb4	125	int "Low address space for LSM to protect from user allocation"
788084ab	126	depends on SECURITY && SECURITY_SELINUX
a58578e4	127	default 65536
788084ab EP	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
1da177e4	140	source security/selinux/Kconfig
e114e473	141	source security/smack/Kconfig
00d7d6f8	142	source security/tomoyo/Kconfig
f9ad1af5	143	source security/apparmor/Kconfig
1da177e4	144
3323eec9 MZ	145	source security/integrity/ima/Kconfig
3323eec9 MZ	146
6e65f92f JJ	147	choice
	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
f9ad1af5	152	default DEFAULT_SECURITY_APPARMOR if SECURITY_APPARMOR
6e65f92f JJ	153	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
f9ad1af5 JJ	168	config DEFAULT_SECURITY_APPARMOR
	169	bool "AppArmor" if SECURITY_APPARMOR=y
	170
6e65f92f JJ	171	config DEFAULT_SECURITY_DAC
	172	bool "Unix Discretionary Access Controls"
	173
	174	endchoice
	175
	176	config 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
f9ad1af5	181	default "apparmor" if DEFAULT_SECURITY_APPARMOR
6e65f92f JJ	182	default "" if DEFAULT_SECURITY_DAC
6e65f92f JJ	183
1da177e4 LT	184	endmenu
1da177e4 LT	185