diff options
author | Dimitri John Ledkov <dimitri.ledkov@canonical.com> | 2023-10-10 22:25:29 +0100 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2023-10-20 13:39:26 +0800 |
commit | d12a6b181866c9fbcd59338e54beb3491846e751 (patch) | |
tree | 8ea2e5a4467a0dc278ce8f2a8c823a5f76133b2d /crypto/asymmetric_keys/pkcs7_verify.c | |
parent | 6add861dcd431e475e24eff95cda1d08d29797ec (diff) | |
download | linux-crypto-d12a6b181866c9fbcd59338e54beb3491846e751.tar.gz linux-crypto-d12a6b181866c9fbcd59338e54beb3491846e751.zip |
crypto: mscode_parser - remove sha224 authenticode support
It is possible to stand up own certificates and sign PE-COFF binaries
using SHA-224. However it never became popular or needed since it has
similar costs as SHA-256. Windows Authenticode infrastructure never
had support for SHA-224, and all secureboot keys used fro linux
vmlinuz have always been using at least SHA-256.
Given the point of mscode_parser is to support interoperatiblity with
typical de-facto hashes, remove support for SHA-224 to avoid
posibility of creating interoperatibility issues with rhboot/shim,
grub, and non-linux systems trying to sign or verify vmlinux.
SHA-224 itself is not removed from the kernel, as it is truncated
SHA-256. If requested I can write patches to remove SHA-224 support
across all of the drivers.
Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/asymmetric_keys/pkcs7_verify.c')
0 files changed, 0 insertions, 0 deletions