Searched hist:"7901 c1a8effbe5f89673bfc09d6e37b8f334f1a7" (Results 1 – 3 of 3) sorted by relevance
| /linux/crypto/asymmetric_keys/ |
| H A D | asymmetric_keys.h | diff 7901c1a8effbe5f89673bfc09d6e37b8f334f1a7 Tue Sep 16 18:36:11 CEST 2014 David Howells <dhowells@redhat.com> 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>
|
| H A D | asymmetric_type.c | diff 7901c1a8effbe5f89673bfc09d6e37b8f334f1a7 Tue Sep 16 18:36:11 CEST 2014 David Howells <dhowells@redhat.com> 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>
|
| /linux/include/keys/ |
| H A D | asymmetric-type.h | diff 7901c1a8effbe5f89673bfc09d6e37b8f334f1a7 Tue Sep 16 18:36:11 CEST 2014 David Howells <dhowells@redhat.com> 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>
|