xref: /openbmc/linux/security/Kconfig (revision e868d61272caa648214046a096e5a6bfc068dc8c)
1#
2# Security configuration
3#
4
5menu "Security options"
6
7config 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
24config KEYS_DEBUG_PROC_KEYS
25	bool "Enable the /proc/keys file by which keys may be viewed"
26	depends on KEYS
27	help
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.
31
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.
41
42config SECURITY
43	bool "Enable different security models"
44	depends on SYSFS
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
54config SECURITY_NETWORK
55	bool "Socket and Networking Security Hooks"
56	depends on SECURITY
57	help
58	  This enables the socket and networking security hooks.
59	  If enabled, a security module can use these hooks to
60	  implement socket and networking access controls.
61	  If you are unsure how to answer this question, answer N.
62
63config SECURITY_NETWORK_XFRM
64	bool "XFRM (IPSec) Networking Security Hooks"
65	depends on XFRM && SECURITY_NETWORK
66	help
67	  This enables the XFRM (IPSec) networking security hooks.
68	  If enabled, a security module can use these hooks to
69	  implement per-packet access controls based on labels
70	  derived from IPSec policy.  Non-IPSec communications are
71	  designated as unlabelled, and only sockets authorized
72	  to communicate unlabelled data can send without using
73	  IPSec.
74	  If you are unsure how to answer this question, answer N.
75
76config SECURITY_CAPABILITIES
77	tristate "Default Linux Capabilities"
78	depends on SECURITY
79	help
80	  This enables the "default" Linux capabilities functionality.
81	  If you are unsure how to answer this question, answer Y.
82
83config SECURITY_ROOTPLUG
84	tristate "Root Plug Support"
85	depends on USB && SECURITY
86	help
87	  This is a sample LSM module that should only be used as such.
88	  It prevents any programs running with egid == 0 if a specific
89	  USB device is not present in the system.
90
91	  See <http://www.linuxjournal.com/article.php?sid=6279> for
92	  more information about this module.
93
94	  If you are unsure how to answer this question, answer N.
95
96source security/selinux/Kconfig
97
98endmenu
99
100