KEYS: Implement binary asymmetric key ID handling
authorDavid Howells <dhowells@redhat.com>
Tue, 16 Sep 2014 16:36:11 +0000 (17:36 +0100)
committerDavid Howells <dhowells@redhat.com>
Tue, 16 Sep 2014 16:36:11 +0000 (17:36 +0100)
commit7901c1a8effbe5f89673bfc09d6e37b8f334f1a7
treed11b8945fe52a9973fa56d9d7aa99a5496a9115f
parentf93b3cc7b1e6f16aedd745a8edba64355383184c
KEYS: Implement binary asymmetric key ID handling

Implement the first step in using binary key IDs for asymmetric keys rather
than hex string keys.

The previously added match data preparsing will be able to convert hex
criterion strings into binary which can then be compared more rapidly.

Further, we actually want more then one ID string per public key.  The problem
is that X.509 certs refer to other X.509 certs by matching Issuer + AuthKeyId
to Subject + SubjKeyId, but PKCS#7 messages match against X.509 Issuer +
SerialNumber.

This patch just provides facilities for a later patch to make use of.

Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
crypto/asymmetric_keys/asymmetric_keys.h
crypto/asymmetric_keys/asymmetric_type.c
include/keys/asymmetric-type.h