← Deutsche Telekom Security GmbH cases
Bugzilla #2083715
Ca Certificate Compliance
Incident
Externally Reported Incident
Policy Document Issue
Telekom Security / DFN: CRL validity period exceeds 10 days by one second
NEW
Deutsche Telekom Security GmbH
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
This case reports that DFN-issued CRLs covering subscriber certificates had a nextUpdate exactly 864,000 seconds after thisUpdate, described as ten days and one second. The reporter says this violates the Baseline Requirements validity interval for CRLs covering subscriber certificates, citing BR Section 7.2 and S/MIME BR Section 4.9.7. The bug was opened as a third-party reported preliminary incident report by Stefan Kirch of Telekom Security. The thread provided here does not show any remediation, closure, or further discussion beyond the initial report.
Chronology
- DFN CRLs covering subscriber certificates were reported as having a validity interval of ten days and one second.
Thread Activity
- Telekom representative — Opened a preliminary incident report stating that DFN CRLs exceeded the allowed validity interval and identified the report as third-party reported.
Participants
Telekom representative
External References
Similar Local Cases
Telekom Security: Failure in automatic issuance of CRLs
Telekom Security / DFN: crlEntryExtensions SEQUENCE of size 0
Telekom Security: Failure to respond to a certificate problem report within 24 hours
Asseco DS / Certum: Delayed preliminary CPR response due to email address typo
SwissSign: Delayed Response to CPR - Bugzilla 2083791
eMudhra emSign PKI Services: CP/CPS documents not updated for current requirements
DigiCert: Publishing timeline for CRL
Telekom Security: OCSP responder uses incorrect signature algorithm for P-384 signing key