[GitHub/mt8127/android_kernel_alcatel_ttab.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 SECURITY_FILE_CAPABILITIES
	bool "File POSIX Capabilities"
	default n
	help
	  This enables filesystem capabilities, allowing you to give
	  binaries a subset of root's powers without using setuid 0.

	  If in doubt, answer N.

config SECURITY_ROOTPLUG
	bool "Root Plug Support"
	depends on USB=y && SECURITY
	help
	  This is a sample LSM module that should only be used as such.
	  It prevents any programs running with egid == 0 if a specific
	  USB device is not present in the system.

	  See <http://www.linuxjournal.com/article.php?sid=6279> for
	  more information about this module.

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

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

source security/integrity/ima/Kconfig

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
b5376771	94	config SECURITY_FILE_CAPABILITIES
84aaa7ab	95	bool "File POSIX Capabilities"
b5376771 SH	96	default n
	97	help
	98	This enables filesystem capabilities, allowing you to give
	99	binaries a subset of root's powers without using setuid 0.
	100
	101	If in doubt, answer N.
	102
1da177e4	103	config SECURITY_ROOTPLUG
20510f2f JM	104	bool "Root Plug Support"
20510f2f JM	105	depends on USB=y && SECURITY
1da177e4 LT	106	help
	107	This is a sample LSM module that should only be used as such.
	108	It prevents any programs running with egid == 0 if a specific
	109	USB device is not present in the system.
	110
	111	See <http://www.linuxjournal.com/article.php?sid=6279> for
	112	more information about this module.
a5ecbcb8	113
e0a94c2a	114	If you are unsure how to answer this question, answer N.
a5ecbcb8	115
1da177e4	116	source security/selinux/Kconfig
e114e473	117	source security/smack/Kconfig
00d7d6f8	118	source security/tomoyo/Kconfig
1da177e4	119
3323eec9 MZ	120	source security/integrity/ima/Kconfig
3323eec9 MZ	121
1da177e4 LT	122	endmenu
1da177e4 LT	123