X.509: If available, use the raw subjKeyId to form the key description
authorDavid Howells <dhowells@redhat.com>
Fri, 3 Oct 2014 15:17:02 +0000 (16:17 +0100)
committerDavid Howells <dhowells@redhat.com>
Fri, 3 Oct 2014 15:17:02 +0000 (16:17 +0100)
commitdd2f6c4481debfa389c1f2b2b1d5bd6449c42611
treeefdec24c56f02377b3edf6660d4775cf0c804e30
parent40b50e80c5ca78b3164d79d39b4889c4e58f462e
X.509: If available, use the raw subjKeyId to form the key description

Module signing matches keys by comparing against the key description exactly.
However, the way the key description gets constructed got changed to be
composed of the subject name plus the certificate serial number instead of the
subject name and the subjectKeyId.  I changed this to avoid problems with
certificates that don't *have* a subjectKeyId.

Instead, if available, use the raw subjectKeyId to form the key description
and only use the serial number if the subjectKeyId doesn't exist.

Reported-by: Dmitry Kasatkin <d.kasatkin@samsung.com>
Signed-off-by: David Howells <dhowells@redhat.com>
crypto/asymmetric_keys/x509_cert_parser.c
crypto/asymmetric_keys/x509_parser.h
crypto/asymmetric_keys/x509_public_key.c