On Tue, 2016-01-19 at 11:30 +0000, David Howells wrote:
> Allow X.509 certs to be blacklisted based on their TBS hash.
What is the TBS hash? This doesn't seem to be the key identifier. The
cert associated with this key identifier is loaded onto the .ima
keyring.
eg: openssl x509 -in <pathname> -inform DER -notext -out
<snip>
X509v3 extensions:
X509v3 Subject Key Identifier:
71:12:39:B3:AB:E6:8D:BF:70:E7:26:DE:C8:4A:3F:5F:17:EF:00:6C
# keyctl show %keyring:.blacklist
Keyring
466574863 ---lswrv 0 0 keyring: .blacklist
433453563 ---lswrv 0 0 \_ blacklist:
711239b3abe68dbf70e726dec84a3f5f17ef006c
Mimi
> This is
> convenient since we have to determine this anyway to be able to check the
> signature on an X.509 certificate.
>
> 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 <dhowe...@redhat.com>
