Re: AuthorityKeyIdentifier and SubjectKeyIdentifier in DRIP X.509 certs

Peter Gutmann <[email protected]> Sun, 14 May 2023 23:30:56 +0000
Newsgroups gmane.ietf.x509
Message-ID <SY4PR01MB625132D16A3FDB3C64E7F2EDEE7B9@SY4PR01MB6251.ausprd01.prod.outlook.com>
Robert Moskowitz <[email protected]> writes:

>I SHOULD be able to use the DETS in keyIdentifier as I do with
>SubjectKeyIdentifier, but openSSL is resisting my efforts.  So far.

The aKID is copied from the issuing cert so I would imagine you can't just set
it arbitrarily.  OTOH since the aKID is copied from the issuing cert the
obvious way to get it into the subject cert would be to set it as the sKID in
the issuing cert.

>I was wondering if there is something I could do with authorityCertIssuer?

Probably not for the same reason you can't set the aKID in the subject cert
yourself.

You then also run into the problem that the sKID/aKID is the universal
identifier there and it's not clear what, if any, support there is for
handling authorityCertIssuers.

Peter.