Kconfig 4.27 KB
Newer Older
Linus Torvalds's avatar
Linus Torvalds committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
#
# 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
25
	bool "Enable the /proc/keys file by which keys may be viewed"
Linus Torvalds's avatar
Linus Torvalds committed
26 27
	depends on KEYS
	help
28 29 30
	  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.
Linus Torvalds's avatar
Linus Torvalds committed
31

32 33 34 35 36 37 38 39 40
	  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.
Linus Torvalds's avatar
Linus Torvalds committed
41 42 43

config SECURITY
	bool "Enable different security models"
44
	depends on SYSFS
Linus Torvalds's avatar
Linus Torvalds committed
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61
	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.
62 63 64 65 66 67 68 69 70 71 72 73 74

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.
Linus Torvalds's avatar
Linus Torvalds committed
75 76

config SECURITY_CAPABILITIES
77
	bool "Default Linux Capabilities"
Linus Torvalds's avatar
Linus Torvalds committed
78
	depends on SECURITY
79
	default y
Linus Torvalds's avatar
Linus Torvalds committed
80 81 82 83
	help
	  This enables the "default" Linux capabilities functionality.
	  If you are unsure how to answer this question, answer Y.

84 85 86 87 88 89 90 91 92 93
config SECURITY_FILE_CAPABILITIES
	bool "File POSIX Capabilities (EXPERIMENTAL)"
	depends on (SECURITY=n || SECURITY_CAPABILITIES!=n) && EXPERIMENTAL
	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.

Linus Torvalds's avatar
Linus Torvalds committed
94
config SECURITY_ROOTPLUG
95 96
	bool "Root Plug Support"
	depends on USB=y && SECURITY
Linus Torvalds's avatar
Linus Torvalds committed
97 98 99 100 101 102 103 104 105 106
	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.

107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124
config SECURITY_DEFAULT_MMAP_MIN_ADDR
        int "Low address space to protect from user allocation"
        depends on SECURITY
        default 0
        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 users with lots of address space a value of 65536 is
	  reasonable and should cause no problems.  Programs which use vm86
	  functionality would either need additional permissions from either
	  the LSM or the capabilities module or have this protection disabled.

	  This value can be changed after boot using the
	  /proc/sys/vm/mmap_min_addr tunable.


Linus Torvalds's avatar
Linus Torvalds committed
125
source security/selinux/Kconfig
126
source security/smack/Kconfig
Linus Torvalds's avatar
Linus Torvalds committed
127 128 129

endmenu