2 # Security configuration
5 menu "Security options"
8 bool "Enable access key retention support"
10 This option provides support for retaining authentication tokens and
11 access keys in the kernel.
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.
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,
22 If you are unsure as to whether this is required, answer N.
24 config KEYS_DEBUG_PROC_KEYS
25 bool "Enable the /proc/keys file by which keys may be viewed"
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
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.
37 Only key attributes are listed here; key payloads are not included in
40 If you are unsure as to whether this is required, answer N.
43 bool "Enable different security models"
46 This allows you to choose different security modules to be
47 configured into your kernel.
49 If this option is not selected, the default Linux security
52 If you are unsure how to answer this question, answer N.
54 config SECURITY_NETWORK
55 bool "Socket and Networking Security Hooks"
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.
63 config SECURITY_NETWORK_XFRM
64 bool "XFRM (IPSec) Networking Security Hooks"
65 depends on XFRM && SECURITY_NETWORK
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
74 If you are unsure how to answer this question, answer N.
76 config SECURITY_CAPABILITIES
77 bool "Default Linux Capabilities"
80 This enables the "default" Linux capabilities functionality.
81 If you are unsure how to answer this question, answer Y.
83 config SECURITY_FILE_CAPABILITIES
84 bool "File POSIX Capabilities (EXPERIMENTAL)"
85 depends on (SECURITY=n || SECURITY_CAPABILITIES!=n) && EXPERIMENTAL
88 This enables filesystem capabilities, allowing you to give
89 binaries a subset of root's powers without using setuid 0.
91 If in doubt, answer N.
93 config SECURITY_ROOTPLUG
94 bool "Root Plug Support"
95 depends on USB=y && SECURITY
97 This is a sample LSM module that should only be used as such.
98 It prevents any programs running with egid == 0 if a specific
99 USB device is not present in the system.
101 See <http://www.linuxjournal.com/article.php?sid=6279> for
102 more information about this module.
104 If you are unsure how to answer this question, answer N.
106 source security/selinux/Kconfig