2menu "Certificates for signature checking"
5 string "File name or PKCS#11 URI of module signing key"
6 default "certs/signing_key.pem"
7 depends on MODULE_SIG || (IMA_APPRAISE_MODSIG && MODULES)
9 Provide the file name of a private key/certificate in PEM format,
10 or a PKCS#11 URI according to RFC7512. The file should contain, or
11 the URI should identify, both the certificate and its corresponding
12 private key.
14 If this option is unchanged from its default "certs/signing_key.pem",
15 then the kernel will automatically generate the private key and
16 certificate as described in Documentation/admin-guide/module-signing.rst
19 bool "Provide system-wide ring of trusted keys"
20 depends on KEYS
21 depends on ASYMMETRIC_KEY_TYPE
23 Provide a system keyring to which trusted keys can be added. Keys in
24 the keyring are considered to be trusted. Keys may be added at will
25 by the kernel from compiled-in data and from hardware key stores, but
26 userspace may only add extra keys if those keys can be verified by
27 keys already in the keyring.
29 Keys in this keyring are used by module signature checking.
32 string "Additional X.509 keys for default system keyring"
33 depends on SYSTEM_TRUSTED_KEYRING
35 If set, this option should be the filename of a PEM-formatted file
36 containing trusted X.509 certificates to be included in the default
37 system keyring. Any certificate used for module signing is implicitly
38 also trusted.
40 NOTE: If you previously provided keys for the system keyring in the
41 form of DER-encoded *.x509 files in the top-level build directory,
42 those are no longer used. You will need to set this option instead.
45 bool "Reserve area for inserting a certificate without recompiling"
46 depends on SYSTEM_TRUSTED_KEYRING
48 If set, space for an extra certificate will be reserved in the kernel
49 image. This allows introducing a trusted certificate to the default
50 system keyring without recompiling the kernel.
53 int "Number of bytes to reserve for the extra certificate"
54 depends on SYSTEM_EXTRA_CERTIFICATE
55 default 4096
57 This is the number of bytes reserved in the kernel image for a
58 certificate to be inserted.
61 bool "Provide a keyring to which extra trustable keys may be added"
62 depends on SYSTEM_TRUSTED_KEYRING
64 If set, provide a keyring to which extra keys may be added, provided
65 those keys are not blacklisted and are vouched for by a key built
66 into the kernel or already in the secondary trusted keyring.
69 bool "Provide system-wide ring of blacklisted keys"
70 depends on KEYS
72 Provide a system keyring to which blacklisted keys can be added.
73 Keys in the keyring are considered entirely untrusted. Keys in this
74 keyring are used by the module signature checking to reject loading
75 of modules signed with a blacklisted key.
78 string "Hashes to be preloaded into the system blacklist keyring"
79 depends on SYSTEM_BLACKLIST_KEYRING
81 If set, this option should be the filename of a list of hashes in the
82 form "<hash>", "<hash>", ... . This will be included into a C
83 wrapper to incorporate the list into the kernel. Each <hash> should
84 be a string of hex digits.
87 bool "Provide system-wide ring of revocation certificates"
88 depends on SYSTEM_BLACKLIST_KEYRING
89 depends on PKCS7_MESSAGE_PARSER=y
91 If set, this allows revocation certificates to be stored in the
92 blacklist keyring and implements a hook whereby a PKCS#7 message can
93 be checked to see if it matches such a certificate.
96 string "X.509 certificates to be preloaded into the system blacklist keyring"
97 depends on SYSTEM_REVOCATION_LIST
99 If set, this option should be the filename of a PEM-formatted file
100 containing X.509 certificates to be included in the default blacklist