[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 all keys may be viewed"
	depends on KEYS
	help
	  This option turns on support for the /proc/keys file through which
	  all the keys on the system can be listed.

	  This option is a slight security risk in that it makes it possible
	  for anyone to see all the keys on the system. Normally the manager
	  pretends keys that are inaccessible to a process don't exist as far
	  as that process is concerned.

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 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_CAPABILITIES
	tristate "Default Linux Capabilities"
	depends on SECURITY
	help
	  This enables the "default" Linux capabilities functionality.
	  If you are unsure how to answer this question, answer Y.

config SECURITY_ROOTPLUG
	tristate "Root Plug Support"
	depends on USB && 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.

config SECURITY_SECLVL
	tristate "BSD Secure Levels"
	depends on SECURITY
	select CRYPTO
	select CRYPTO_SHA1
	help
	  Implements BSD Secure Levels as an LSM.  See
	  <file:Documentation/seclvl.txt> for instructions on how to use this
	  module.

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

source security/selinux/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
	25	bool "Enable the /proc/keys file by which all keys may be viewed"
	26	depends on KEYS
	27	help
	28	This option turns on support for the /proc/keys file through which
	29	all the keys on the system can be listed.
	30
	31	This option is a slight security risk in that it makes it possible
	32	for anyone to see all the keys on the system. Normally the manager
	33	pretends keys that are inaccessible to a process don't exist as far
	34	as that process is concerned.
	35
	36	config SECURITY
	37	bool "Enable different security models"
2c40579b	38	depends on SYSFS
1da177e4 LT	39	help
	40	This allows you to choose different security modules to be
	41	configured into your kernel.
	42
	43	If this option is not selected, the default Linux security
	44	model will be used.
	45
	46	If you are unsure how to answer this question, answer N.
	47
	48	config SECURITY_NETWORK
	49	bool "Socket and Networking Security Hooks"
	50	depends on SECURITY
	51	help
	52	This enables the socket and networking security hooks.
	53	If enabled, a security module can use these hooks to
	54	implement socket and networking access controls.
	55	If you are unsure how to answer this question, answer N.
df71837d TJ	56
	57	config SECURITY_NETWORK_XFRM
	58	bool "XFRM (IPSec) Networking Security Hooks"
	59	depends on XFRM && SECURITY_NETWORK
	60	help
	61	This enables the XFRM (IPSec) networking security hooks.
	62	If enabled, a security module can use these hooks to
	63	implement per-packet access controls based on labels
	64	derived from IPSec policy. Non-IPSec communications are
	65	designated as unlabelled, and only sockets authorized
	66	to communicate unlabelled data can send without using
	67	IPSec.
	68	If you are unsure how to answer this question, answer N.
1da177e4 LT	69
	70	config SECURITY_CAPABILITIES
	71	tristate "Default Linux Capabilities"
	72	depends on SECURITY
	73	help
	74	This enables the "default" Linux capabilities functionality.
	75	If you are unsure how to answer this question, answer Y.
	76
	77	config SECURITY_ROOTPLUG
	78	tristate "Root Plug Support"
	79	depends on USB && SECURITY
	80	help
	81	This is a sample LSM module that should only be used as such.
	82	It prevents any programs running with egid == 0 if a specific
	83	USB device is not present in the system.
	84
	85	See <http://www.linuxjournal.com/article.php?sid=6279> for
	86	more information about this module.
	87
	88	If you are unsure how to answer this question, answer N.
	89
	90	config SECURITY_SECLVL
	91	tristate "BSD Secure Levels"
	92	depends on SECURITY
	93	select CRYPTO
	94	select CRYPTO_SHA1
	95	help
	96	Implements BSD Secure Levels as an LSM. See
	97	<file:Documentation/seclvl.txt> for instructions on how to use this
	98	module.
	99
	100	If you are unsure how to answer this question, answer N.
	101
	102	source security/selinux/Kconfig
	103
	104	endmenu
	105