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 7 select ASSOCIATIVE_ARRAY
9 help 8 help
10 This option provides support for ret 9 This option provides support for retaining authentication tokens and
11 access keys in the kernel. 10 access keys in the kernel.
12 11
13 It also includes provision of method 12 It also includes provision of methods by which such keys might be
14 associated with a process so that ne 13 associated with a process so that network filesystems, encryption
15 support and the like can find them. 14 support and the like can find them.
16 15
17 Furthermore, a special type of key i 16 Furthermore, a special type of key is available that acts as keyring:
18 a searchable sequence of keys. Each 17 a searchable sequence of keys. Each process is equipped with access
19 to five standard keyrings: UID-speci 18 to five standard keyrings: UID-specific, GID-specific, session,
20 process and thread. 19 process and thread.
21 20
22 If you are unsure as to whether this 21 If you are unsure as to whether this is required, answer N.
23 22
24 config KEYS_REQUEST_CACHE !! 23 config KEYS_COMPAT
25 bool "Enable temporary caching of the !! 24 def_bool y
26 depends on KEYS !! 25 depends on COMPAT && 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 26
42 config PERSISTENT_KEYRINGS 27 config PERSISTENT_KEYRINGS
43 bool "Enable register of persistent pe 28 bool "Enable register of persistent per-UID keyrings"
44 depends on KEYS 29 depends on KEYS
45 help 30 help
46 This option provides a register of p 31 This option provides a register of persistent per-UID keyrings,
47 primarily aimed at Kerberos key stor 32 primarily aimed at Kerberos key storage. The keyrings are persistent
48 in the sense that they stay around a 33 in the sense that they stay around after all processes of that UID
49 have exited, not that they survive t 34 have exited, not that they survive the machine being rebooted.
50 35
51 A particular keyring may be accessed 36 A particular keyring may be accessed by either the user whose keyring
52 it is or by a process with administr 37 it is or by a process with administrative privileges. The active
53 LSMs gets to rule on which admin-lev 38 LSMs gets to rule on which admin-level processes get to access the
54 cache. 39 cache.
55 40
56 Keyrings are created and added into 41 Keyrings are created and added into the register upon demand and get
57 removed if they expire (a default ti 42 removed if they expire (a default timeout is set upon creation).
58 43
59 config BIG_KEYS 44 config BIG_KEYS
60 bool "Large payload keys" 45 bool "Large payload keys"
61 depends on KEYS 46 depends on KEYS
62 depends on TMPFS 47 depends on TMPFS
63 depends on CRYPTO_LIB_CHACHA20POLY1305 <<
64 help 48 help
65 This option provides support for hol 49 This option provides support for holding large keys within the kernel
66 (for example Kerberos ticket caches) 50 (for example Kerberos ticket caches). The data may be stored out to
67 swapspace by tmpfs. 51 swapspace by tmpfs.
68 52
69 If you are unsure as to whether this 53 If you are unsure as to whether this is required, answer N.
70 54
71 config TRUSTED_KEYS 55 config TRUSTED_KEYS
72 tristate "TRUSTED KEYS" 56 tristate "TRUSTED KEYS"
73 depends on KEYS !! 57 depends on KEYS && TCG_TPM
>> 58 select CRYPTO
>> 59 select CRYPTO_HMAC
>> 60 select CRYPTO_SHA1
74 help 61 help
75 This option provides support for cre 62 This option provides support for creating, sealing, and unsealing
76 keys in the kernel. Trusted keys are 63 keys in the kernel. Trusted keys are random number symmetric keys,
77 generated and sealed by a trust sour !! 64 generated and RSA-sealed by the TPM. The TPM only unseals the keys,
78 Userspace will only ever see encrypt !! 65 if the boot PCRs and other criteria match. Userspace will only ever
>> 66 see encrypted blobs.
79 67
80 If you are unsure as to whether this 68 If you are unsure as to whether this is required, answer N.
81 69
82 if TRUSTED_KEYS <<
83 source "security/keys/trusted-keys/Kconfig" <<
84 endif <<
85 <<
86 config ENCRYPTED_KEYS 70 config ENCRYPTED_KEYS
87 tristate "ENCRYPTED KEYS" 71 tristate "ENCRYPTED KEYS"
88 depends on KEYS 72 depends on KEYS
89 select CRYPTO 73 select CRYPTO
90 select CRYPTO_HMAC 74 select CRYPTO_HMAC
91 select CRYPTO_AES 75 select CRYPTO_AES
92 select CRYPTO_CBC 76 select CRYPTO_CBC
93 select CRYPTO_SHA256 77 select CRYPTO_SHA256
94 select CRYPTO_RNG 78 select CRYPTO_RNG
95 help 79 help
96 This option provides support for cre 80 This option provides support for create/encrypting/decrypting keys
97 in the kernel. Encrypted keys are i !! 81 in the kernel. Encrypted keys are kernel generated random numbers,
98 generated random numbers or provided !! 82 which are encrypted/decrypted with a 'master' symmetric key. The
99 encrypted/decrypted with a 'master' !! 83 'master' key can be either a trusted-key or user-key type.
100 key can be either a trusted-key or u !! 84 Userspace only ever sees/stores encrypted blobs.
101 blobs are ever output to Userspace. <<
102 85
103 If you are unsure as to whether this 86 If you are unsure as to whether this is required, answer N.
104 <<
105 config USER_DECRYPTED_DATA <<
106 bool "Allow encrypted keys with user d <<
107 depends on ENCRYPTED_KEYS <<
108 help <<
109 This option provides support for ins <<
110 user-provided decrypted data. The d <<
111 encoded. <<
112 <<
113 If you are unsure as to whether this <<
114 <<
115 config KEY_DH_OPERATIONS <<
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.