]>
Commit | Line | Data |
---|---|---|
f0894940 DH |
1 | # |
2 | # Key management configuration | |
3 | # | |
4 | ||
5 | config KEYS | |
6 | bool "Enable access key retention support" | |
b2a4df20 | 7 | select ASSOCIATIVE_ARRAY |
f0894940 DH |
8 | help |
9 | This option provides support for retaining authentication tokens and | |
10 | access keys in the kernel. | |
11 | ||
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. | |
15 | ||
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, | |
19 | process and thread. | |
20 | ||
21 | If you are unsure as to whether this is required, answer N. | |
22 | ||
23 | config TRUSTED_KEYS | |
24 | tristate "TRUSTED KEYS" | |
25 | depends on KEYS && TCG_TPM | |
26 | select CRYPTO | |
27 | select CRYPTO_HMAC | |
28 | select CRYPTO_SHA1 | |
29 | help | |
30 | This option provides support for creating, sealing, and unsealing | |
31 | keys in the kernel. Trusted keys are random number symmetric keys, | |
32 | generated and RSA-sealed by the TPM. The TPM only unseals the keys, | |
33 | if the boot PCRs and other criteria match. Userspace will only ever | |
34 | see encrypted blobs. | |
35 | ||
36 | If you are unsure as to whether this is required, answer N. | |
37 | ||
38 | config ENCRYPTED_KEYS | |
39 | tristate "ENCRYPTED KEYS" | |
40 | depends on KEYS | |
41 | select CRYPTO | |
42 | select CRYPTO_HMAC | |
43 | select CRYPTO_AES | |
44 | select CRYPTO_CBC | |
45 | select CRYPTO_SHA256 | |
46 | select CRYPTO_RNG | |
47 | help | |
48 | This option provides support for create/encrypting/decrypting keys | |
49 | in the kernel. Encrypted keys are kernel generated random numbers, | |
50 | which are encrypted/decrypted with a 'master' symmetric key. The | |
51 | 'master' key can be either a trusted-key or user-key type. | |
52 | Userspace only ever sees/stores encrypted blobs. | |
53 | ||
54 | If you are unsure as to whether this is required, answer N. | |
55 | ||
56 | config KEYS_DEBUG_PROC_KEYS | |
57 | bool "Enable the /proc/keys file by which keys may be viewed" | |
58 | depends on KEYS | |
59 | help | |
60 | This option turns on support for the /proc/keys file - through which | |
61 | can be listed all the keys on the system that are viewable by the | |
62 | reading process. | |
63 | ||
64 | The only keys included in the list are those that grant View | |
65 | permission to the reading process whether or not it possesses them. | |
66 | Note that LSM security checks are still performed, and may further | |
67 | filter out keys that the current process is not authorised to view. | |
68 | ||
69 | Only key attributes are listed here; key payloads are not included in | |
70 | the resulting table. | |
71 | ||
72 | If you are unsure as to whether this is required, answer N. |