1 # SPDX-License-Identifier: GPL-2.0-only <<
2 # 1 #
3 # Key management configuration 2 # Key management configuration
4 # 3 #
5 4
6 config KEYS 5 config KEYS
7 bool "Enable access key retention supp 6 bool "Enable access key retention support"
8 select ASSOCIATIVE_ARRAY <<
9 help 7 help
10 This option provides support for ret 8 This option provides support for retaining authentication tokens and
11 access keys in the kernel. 9 access keys in the kernel.
12 10
13 It also includes provision of method 11 It also includes provision of methods by which such keys might be
14 associated with a process so that ne 12 associated with a process so that network filesystems, encryption
15 support and the like can find them. 13 support and the like can find them.
16 14
17 Furthermore, a special type of key i 15 Furthermore, a special type of key is available that acts as keyring:
18 a searchable sequence of keys. Each 16 a searchable sequence of keys. Each process is equipped with access
19 to five standard keyrings: UID-speci 17 to five standard keyrings: UID-specific, GID-specific, session,
20 process and thread. 18 process and thread.
21 19
22 If you are unsure as to whether this 20 If you are unsure as to whether this is required, answer N.
23 21
24 config KEYS_REQUEST_CACHE <<
25 bool "Enable temporary caching of the <<
26 depends on KEYS <<
27 help <<
28 This option causes the result of the <<
29 call that didn't upcall to the kerne <<
30 task_struct. The cache is cleared b <<
31 resumption of userspace. <<
32 <<
33 This allows the key used for multipl <<
34 wants to request a key that is likel <<
35 by the last step to save on the sear <<
36 <<
37 An example of such a process is a pa <<
38 filesystem in which each method need <<
39 key. Pathwalk will call multiple me <<
40 (permission, d_revalidate, lookup, g <<
41 <<
42 config PERSISTENT_KEYRINGS <<
43 bool "Enable register of persistent pe <<
44 depends on KEYS <<
45 help <<
46 This option provides a register of p <<
47 primarily aimed at Kerberos key stor <<
48 in the sense that they stay around a <<
49 have exited, not that they survive t <<
50 <<
51 A particular keyring may be accessed <<
52 it is or by a process with administr <<
53 LSMs gets to rule on which admin-lev <<
54 cache. <<
55 <<
56 Keyrings are created and added into <<
57 removed if they expire (a default ti <<
58 <<
59 config BIG_KEYS <<
60 bool "Large payload keys" <<
61 depends on KEYS <<
62 depends on TMPFS <<
63 depends on CRYPTO_LIB_CHACHA20POLY1305 <<
64 help <<
65 This option provides support for hol <<
66 (for example Kerberos ticket caches) <<
67 swapspace by tmpfs. <<
68 <<
69 If you are unsure as to whether this <<
70 <<
71 config TRUSTED_KEYS 22 config TRUSTED_KEYS
72 tristate "TRUSTED KEYS" 23 tristate "TRUSTED KEYS"
73 depends on KEYS !! 24 depends on KEYS && TCG_TPM
>> 25 select CRYPTO
>> 26 select CRYPTO_HMAC
>> 27 select CRYPTO_SHA1
74 help 28 help
75 This option provides support for cre 29 This option provides support for creating, sealing, and unsealing
76 keys in the kernel. Trusted keys are 30 keys in the kernel. Trusted keys are random number symmetric keys,
77 generated and sealed by a trust sour !! 31 generated and RSA-sealed by the TPM. The TPM only unseals the keys,
78 Userspace will only ever see encrypt !! 32 if the boot PCRs and other criteria match. Userspace will only ever
>> 33 see encrypted blobs.
79 34
80 If you are unsure as to whether this 35 If you are unsure as to whether this is required, answer N.
81 36
82 if TRUSTED_KEYS <<
83 source "security/keys/trusted-keys/Kconfig" <<
84 endif <<
85 <<
86 config ENCRYPTED_KEYS 37 config ENCRYPTED_KEYS
87 tristate "ENCRYPTED KEYS" 38 tristate "ENCRYPTED KEYS"
88 depends on KEYS 39 depends on KEYS
89 select CRYPTO 40 select CRYPTO
90 select CRYPTO_HMAC 41 select CRYPTO_HMAC
91 select CRYPTO_AES 42 select CRYPTO_AES
92 select CRYPTO_CBC 43 select CRYPTO_CBC
93 select CRYPTO_SHA256 44 select CRYPTO_SHA256
94 select CRYPTO_RNG 45 select CRYPTO_RNG
95 help 46 help
96 This option provides support for cre 47 This option provides support for create/encrypting/decrypting keys
97 in the kernel. Encrypted keys are i !! 48 in the kernel. Encrypted keys are kernel generated random numbers,
98 generated random numbers or provided !! 49 which are encrypted/decrypted with a 'master' symmetric key. The
99 encrypted/decrypted with a 'master' !! 50 'master' key can be either a trusted-key or user-key type.
100 key can be either a trusted-key or u !! 51 Userspace only ever sees/stores encrypted blobs.
101 blobs are ever output to Userspace. <<
102 52
103 If you are unsure as to whether this 53 If you are unsure as to whether this is required, answer N.
104 54
105 config USER_DECRYPTED_DATA !! 55 config KEYS_DEBUG_PROC_KEYS
106 bool "Allow encrypted keys with user d !! 56 bool "Enable the /proc/keys file by which keys may be viewed"
107 depends on ENCRYPTED_KEYS !! 57 depends on KEYS
108 help 58 help
109 This option provides support for ins !! 59 This option turns on support for the /proc/keys file - through which
110 user-provided decrypted data. The d !! 60 can be listed all the keys on the system that are viewable by the
111 encoded. !! 61 reading process.
>> 62
>> 63 The only keys included in the list are those that grant View
>> 64 permission to the reading process whether or not it possesses them.
>> 65 Note that LSM security checks are still performed, and may further
>> 66 filter out keys that the current process is not authorised to view.
112 67
113 If you are unsure as to whether this !! 68 Only key attributes are listed here; key payloads are not included in
>> 69 the resulting table.
114 70
115 config KEY_DH_OPERATIONS !! 71 If you are unsure as to whether this is required, answer N.
116 bool "Diffie-Hellman operations on reta <<
117 depends on KEYS <<
118 select CRYPTO <<
119 select CRYPTO_KDF800108_CTR <<
120 select CRYPTO_DH <<
121 help <<
122 This option provides support for calc <<
123 public keys and shared secrets using <<
124 in the kernel. <<
125 <<
126 If you are unsure as to whether this <<
127 <<
128 config KEY_NOTIFICATIONS <<
129 bool "Provide key/keyring change notif <<
130 depends on KEYS && WATCH_QUEUE <<
131 help <<
132 This option provides support for get <<
133 on keys and keyrings on which the ca <<
134 This makes use of pipes to handle th <<
135 provides KEYCTL_WATCH_KEY to enable/ <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.