Skip to content

Commit f2b88ba

Browse files
xnoxherbertx
authored andcommitted
Documentation/module-signing.txt: bring up to date
Update the documentation to mention that ECC NIST P-384 automatic keypair generation is available to use ECDSA signature type, in addition to the RSA. Drop mentions of the now removed SHA-1 and SHA-224 options. Add the just added FIPS 202 SHA-3 module signature hashes. Signed-off-by: Dimitri John Ledkov <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
1 parent 446b1e0 commit f2b88ba

File tree

1 file changed

+11
-6
lines changed

1 file changed

+11
-6
lines changed

Documentation/admin-guide/module-signing.rst

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,10 @@ trusted userspace bits.
2828

2929
This facility uses X.509 ITU-T standard certificates to encode the public keys
3030
involved. The signatures are not themselves encoded in any industrial standard
31-
type. The facility currently only supports the RSA public key encryption
32-
standard (though it is pluggable and permits others to be used). The possible
33-
hash algorithms that can be used are SHA-1, SHA-224, SHA-256, SHA-384, and
34-
SHA-512 (the algorithm is selected by data in the signature).
31+
type. The built-in facility currently only supports the RSA & NIST P-384 ECDSA
32+
public key signing standard (though it is pluggable and permits others to be
33+
used). The possible hash algorithms that can be used are SHA-2 and SHA-3 of
34+
sizes 256, 384, and 512 (the algorithm is selected by data in the signature).
3535

3636

3737
==========================
@@ -81,11 +81,12 @@ This has a number of options available:
8181
sign the modules with:
8282

8383
=============================== ==========================================
84-
``CONFIG_MODULE_SIG_SHA1`` :menuselection:`Sign modules with SHA-1`
85-
``CONFIG_MODULE_SIG_SHA224`` :menuselection:`Sign modules with SHA-224`
8684
``CONFIG_MODULE_SIG_SHA256`` :menuselection:`Sign modules with SHA-256`
8785
``CONFIG_MODULE_SIG_SHA384`` :menuselection:`Sign modules with SHA-384`
8886
``CONFIG_MODULE_SIG_SHA512`` :menuselection:`Sign modules with SHA-512`
87+
``CONFIG_MODULE_SIG_SHA3_256`` :menuselection:`Sign modules with SHA3-256`
88+
``CONFIG_MODULE_SIG_SHA3_384`` :menuselection:`Sign modules with SHA3-384`
89+
``CONFIG_MODULE_SIG_SHA3_512`` :menuselection:`Sign modules with SHA3-512`
8990
=============================== ==========================================
9091

9192
The algorithm selected here will also be built into the kernel (rather
@@ -145,6 +146,10 @@ into vmlinux) using parameters in the::
145146

146147
file (which is also generated if it does not already exist).
147148

149+
One can select between RSA (``MODULE_SIG_KEY_TYPE_RSA``) and ECDSA
150+
(``MODULE_SIG_KEY_TYPE_ECDSA``) to generate either RSA 4k or NIST
151+
P-384 keypair.
152+
148153
It is strongly recommended that you provide your own x509.genkey file.
149154

150155
Most notably, in the x509.genkey file, the req_distinguished_name section

0 commit comments

Comments
 (0)