diff options
| author | David Howells <dhowells@redhat.com> | 2017-04-03 16:07:25 +0100 |
|---|---|---|
| committer | David Howells <dhowells@redhat.com> | 2017-04-03 16:07:25 +0100 |
| commit | 436529562df2748fd9918f578205b22cf8ced277 (patch) | |
| tree | 77f4f2caa2bba71fb9ca77141041acd398c74497 /usr | |
| parent | 734114f8782f6c3398762f2353fe9101d87b6d06 (diff) | |
| download | linux-next-436529562df2748fd9918f578205b22cf8ced277.tar.gz | |
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>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions