2 # Key management configuration
6 bool "Enable access key retention support"
7 select ASSOCIATIVE_ARRAY
9 This option provides support for retaining authentication tokens and
10 access keys in the kernel.
12 It also includes provision of methods by which such keys might be
13 associated with a process so that network filesystems, encryption
14 support and the like can find them.
16 Furthermore, a special type of key is available that acts as keyring:
17 a searchable sequence of keys. Each process is equipped with access
18 to five standard keyrings: UID-specific, GID-specific, session,
21 If you are unsure as to whether this is required, answer N.
23 config PERSISTENT_KEYRINGS
24 bool "Enable register of persistent per-UID keyrings"
27 This option provides a register of persistent per-UID keyrings,
28 primarily aimed at Kerberos key storage. The keyrings are persistent
29 in the sense that they stay around after all processes of that UID
30 have exited, not that they survive the machine being rebooted.
32 A particular keyring may be accessed by either the user whose keyring
33 it is or by a process with administrative privileges. The active
34 LSMs gets to rule on which admin-level processes get to access the
37 Keyrings are created and added into the register upon demand and get
38 removed if they expire (a default timeout is set upon creation).
41 bool "Large payload keys"
44 depends on (CRYPTO_ANSI_CPRNG = y || CRYPTO_DRBG = y)
49 This option provides support for holding large keys within the kernel
50 (for example Kerberos ticket caches). The data may be stored out to
53 If you are unsure as to whether this is required, answer N.
56 tristate "TRUSTED KEYS"
57 depends on KEYS && TCG_TPM
61 select CRYPTO_HASH_INFO
63 This option provides support for creating, sealing, and unsealing
64 keys in the kernel. Trusted keys are random number symmetric keys,
65 generated and RSA-sealed by the TPM. The TPM only unseals the keys,
66 if the boot PCRs and other criteria match. Userspace will only ever
69 If you are unsure as to whether this is required, answer N.
72 tristate "ENCRYPTED KEYS"
81 This option provides support for create/encrypting/decrypting keys
82 in the kernel. Encrypted keys are kernel generated random numbers,
83 which are encrypted/decrypted with a 'master' symmetric key. The
84 'master' key can be either a trusted-key or user-key type.
85 Userspace only ever sees/stores encrypted blobs.
87 If you are unsure as to whether this is required, answer N.
89 config KEY_DH_OPERATIONS
90 bool "Diffie-Hellman operations on retained keys"
94 This option provides support for calculating Diffie-Hellman
95 public keys and shared secrets using values stored as keys
98 If you are unsure as to whether this is required, answer N.