diff options
author | David Howells <dhowells@redhat.com> | 2015-07-20 22:16:32 +0200 |
---|---|---|
committer | David Howells <dhowells@redhat.com> | 2015-08-12 18:01:01 +0200 |
commit | a4c6e57f4f5fa65cbdb8cc1c14ff5ca7c56766c3 (patch) | |
tree | b58633416215ee7c0fb6e5b7900877cbff934f02 /kernel/kcmp.c | |
parent | PKCS#7: Check content type and versions (diff) | |
download | linux-a4c6e57f4f5fa65cbdb8cc1c14ff5ca7c56766c3.tar.xz linux-a4c6e57f4f5fa65cbdb8cc1c14ff5ca7c56766c3.zip |
X.509: Change recorded SKID & AKID to not include Subject or Issuer
The key identifiers fabricated from an X.509 certificate are currently:
(A) Concatenation of serial number and issuer
(B) Concatenation of subject and subjectKeyID (SKID)
When verifying one X.509 certificate with another, the AKID in the target
can be used to match the authoritative certificate. The AKID can specify
the match in one or both of two ways:
(1) Compare authorityCertSerialNumber and authorityCertIssuer from the AKID
to identifier (A) above.
(2) Compare keyIdentifier from the AKID plus the issuer from the target
certificate to identifier (B) above.
When verifying a PKCS#7 message, the only available comparison is between
the IssuerAndSerialNumber field and identifier (A) above.
However, a subsequent patch adds CMS support. Whilst CMS still supports a
match on IssuerAndSerialNumber as for PKCS#7, it also supports an
alternative - which is the SubjectKeyIdentifier field. This is used to
match to an X.509 certificate on the SKID alone. No subject information is
available to be used.
To this end change the fabrication of (B) above to be from the X.509 SKID
alone. The AKID in keyIdentifier form then only matches on that and does
not include the issuer.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-By: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'kernel/kcmp.c')
0 files changed, 0 insertions, 0 deletions