2 # Security configuration
5 menu "Security options"
8 bool "Enable access key retention support"
9 depends on !VSERVER_SECURITY
11 This option provides support for retaining authentication tokens and
12 access keys in the kernel.
14 It also includes provision of methods by which such keys might be
15 associated with a process so that network filesystems, encryption
16 support and the like can find them.
18 Furthermore, a special type of key is available that acts as keyring:
19 a searchable sequence of keys. Each process is equipped with access
20 to five standard keyrings: UID-specific, GID-specific, session,
23 If you are unsure as to whether this is required, answer N.
25 config KEYS_DEBUG_PROC_KEYS
26 bool "Enable the /proc/keys file by which keys may be viewed"
29 This option turns on support for the /proc/keys file - through which
30 can be listed all the keys on the system that are viewable by the
33 The only keys included in the list are those that grant View
34 permission to the reading process whether or not it possesses them.
35 Note that LSM security checks are still performed, and may further
36 filter out keys that the current process is not authorised to view.
38 Only key attributes are listed here; key payloads are not included in
41 If you are unsure as to whether this is required, answer N.
44 bool "Enable different security models"
47 This allows you to choose different security modules to be
48 configured into your kernel.
50 If this option is not selected, the default Linux security
53 If you are unsure how to answer this question, answer N.
55 config SECURITY_NETWORK
56 bool "Socket and Networking Security Hooks"
59 This enables the socket and networking security hooks.
60 If enabled, a security module can use these hooks to
61 implement socket and networking access controls.
62 If you are unsure how to answer this question, answer N.
64 config SECURITY_NETWORK_XFRM
65 bool "XFRM (IPSec) Networking Security Hooks"
66 depends on XFRM && SECURITY_NETWORK
68 This enables the XFRM (IPSec) networking security hooks.
69 If enabled, a security module can use these hooks to
70 implement per-packet access controls based on labels
71 derived from IPSec policy. Non-IPSec communications are
72 designated as unlabelled, and only sockets authorized
73 to communicate unlabelled data can send without using
75 If you are unsure how to answer this question, answer N.
77 config SECURITY_CAPABILITIES
78 tristate "Default Linux Capabilities"
81 This enables the "default" Linux capabilities functionality.
82 If you are unsure how to answer this question, answer Y.
84 config SECURITY_ROOTPLUG
85 tristate "Root Plug Support"
86 depends on USB && SECURITY
88 This is a sample LSM module that should only be used as such.
89 It prevents any programs running with egid == 0 if a specific
90 USB device is not present in the system.
92 See <http://www.linuxjournal.com/article.php?sid=6279> for
93 more information about this module.
95 If you are unsure how to answer this question, answer N.
97 source security/selinux/Kconfig