← DigiCert cases
Bugzilla #2081712
Ca Certificate Compliance
Incident
Externally Reported Incident
Delayed Revocation
DigiCert report on CRL publication timing after revocation
ASSIGNED
DigiCert
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update.
Always refer to the official Bugzilla thread as the authoritative source.
If you spot an inaccuracy, let me know via the contact form.
AI Summary
DigiCert opened this bug as a preliminary incident report about CRL publication timing. The thread says DigiCert received a third-party report that a CRL version was first published 24 hours, 3 minutes, and 18 seconds after the revocationDate for a certificate included in that CRL. DigiCert cites BR Section 4.9.7, which requires a CA to update and publish a new CRL within 24 hours after recording a certificate as revoked. The case is about the timing obligation for CRL publication, not about the underlying certificate content. The bug remains assigned, and no resolution is stated in the thread excerpt.
Chronology
- A CRL version was first published 24 hours, 3 minutes, and 18 seconds after the revocationDate for a revoked certificate.
Thread Activity
- DigiCert — DigiCert filed a preliminary incident report stating that a third party reported the CRL publication occurred after the 24-hour deadline in BR Section 4.9.7.
Participants
DigiCert
External References
Similar Local Cases
DigiCert: Expired CRL
DigiCert: Delayed availability of OCSP responses
DigiCert: OCSP returns unauthorized for an issued TLS Certificate
QuoVadis: revocation services validity set to expected value plus one second
DigiCert: Delayed response to problem report related to Bug 2055539
Actalis: Root CA CRL not published within 24 hours after recording revocations
SwissSign: Delayed Response to CPR - Bugzilla 2083791
IZENPE: revocation reason code not included in CRL issued by Root