← e-tugra cases
Bugzilla #1687608
Certificate Problem Report
E-Tugra: The failure to revoke a certificate
RESOLVED
FIXED
e-tugra
AI Summary
E-Tugra faced a failure to revoke a certificate within the mandated timeframe after discovering an issue with the common name not being included in the Subject Alternative Name (SAN). The certificate was issued on December 23, 2020, and the problem was identified on December 24, 2020. Although the revocation was completed on January 18, 2021, it was not executed within the required five days. E-Tugra has since implemented additional controls to prevent similar issues in the future, including enhanced pre-issuance linting and a new workflow for error handling.
Chronology
- Certificate issued
- Problem identified and new certificate issued
- Email received regarding revocation
- Certificate revoked
- Bug created to address the issue
- New controls implemented in production
Participants
Davut Tokgöz
George
External References
Similar Local Cases
E-Tugra: Delayed Response of Revocation Request
E-Tugra: commonName not in SAN
E-Tugra: Validity period > 825 days
E-Tugra: Intermittent OCSP response with status 'Unknown'
E-Tugra: Insufficient serial number entropy
Actalis: inaccurate value in stateOrProvinceName
QuoVadis: BR Error - san dns name starts with period
certSIGN: Delayed revocation