Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct the reasons for not needing the AIA in OCSP certificates #480

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hablutzel1
Copy link

From https://datatracker.ietf.org/doc/html/rfc6960#section-4.1.1:

4.1.1. ASN.1 Specification of the OCSP Request
...
CertID ::= SEQUENCE {
hashAlgorithm AlgorithmIdentifier,
issuerNameHash OCTET STRING, -- Hash of issuer's DN
issuerKeyHash OCTET STRING, -- Hash of issuer's public key
serialNumber CertificateSerialNumber }
...
The contents of CertID include the following fields:
...
o issuerNameHash is the hash of the issuer's distinguished name
(DN). The hash shall be calculated over the DER encoding of the
issuer's name field in the certificate being checked.
o issuerKeyHash is the hash of the issuer's public key. The hash
shall be calculated over the value (excluding tag and length) of
the subject public key field in the issuer's certificate.
o serialNumber is the serial number of the certificate for which
status is being requested.

From https://datatracker.ietf.org/doc/html/rfc6960#section-4.2.2.2.1:

4.2.2.2.1. Revocation Checking of an Authorized Responder
...

  • A CA may specify that an OCSP client can trust a responder for the
    lifetime of the responder's certificate. The CA does so by
    including the extension id-pkix-ocsp-nocheck.

@hablutzel1 hablutzel1 requested a review from a team as a code owner February 5, 2024 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant