X.509: Allow X.509 certs to be blacklisted
authorDavid Howells <dhowells@redhat.com>
Thu, 1 Sep 2016 10:02:41 +0000 (11:02 +0100)
committerDavid Howells <dhowells@redhat.com>
Thu, 1 Sep 2016 10:02:41 +0000 (11:02 +0100)
commit98a1b4feb82ee3ab86f0c6323685977de9ec6f5a
tree14b7d348706fad34b97c7caabb95526a00d56d39
parent8dada209fda3d8bacf6fc0fdd01fd6cb603de540
X.509: Allow X.509 certs to be blacklisted

Allow X.509 certs to be blacklisted based on their TBSCertificate hash.
This is convenient since we have to determine this anyway to be able to
check the signature on an X.509 certificate.  This is also what UEFI uses
in its blacklist.

If a certificate built into the kernel is blacklisted, something like the
following might then be seen during boot:

X.509: Cert 123412341234c55c1dcc601ab8e172917706aa32fb5eaf826813547fdf02dd46 is blacklisted
Problem loading in-kernel X.509 certificate (-129)

where the hex string shown is the blacklisted hash.

Signed-off-by: David Howells <dhowells@redhat.com>
crypto/asymmetric_keys/x509_parser.h
crypto/asymmetric_keys/x509_public_key.c
This page took 0.024508 seconds and 5 git commands to generate.