← Netlock cases
Bugzilla #1938167 Incident

NETLOCK: CRL not published in DER Encoded Format

RESOLVED FIXED Netlock
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

NETLOCK reported a compliance issue regarding the encoding of Certificate Revocation Lists (CRLs) published in PEM format instead of the required DER format, violating RFC 5280. The issue was identified on December 17, 2024, and NETLOCK promptly changed the encoding format to DER on December 18, 2024. They confirmed that no subscribers were impacted by this issue, as the certificates were not malformed. NETLOCK has since implemented a new validation process to prevent future encoding errors, including the integration of a linter for ongoing compliance checks. All action items related to this incident have been completed, and NETLOCK has requested closure of the case.

Model: gpt-4o-mini Generated: 2026-06-13 21:03 UTC Revised: 2026-06-16 18:50 UTC Confidence: 0.90 16 comments
Chronology
  1. Notification received about improperly encoded CRLs.
  2. NETLOCK changed the CRL encoding from PEM to DER.
  3. Implementation of the pkimetal linter for validation completed.
Thread Activity
  1. Netlock — Preliminary Incident Report submitted detailing the CRL encoding issue.
  2. Netlock — Incident Report submitted with further details and action items.
  3. Netlock — Request for closure submitted after completing all action items.
Participants
Netlock Jesperkristensen representative Sectigo Mozilla representative CCADB representative
External References
Similar Local Cases
#2013400 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-04-17 · 98% similar
NETLOCK: did not file a preliminary incident report or respond to a third-party report within the 72-hour timeframe
#2013395 RESOLVED Self Reported Incident Incident Opened 2026-01-29 · Closed 2026-05-26 · 94% similar
NETLOCK: Missing Related Incidents section in the bug report
#1819105 RESOLVED Incident Opened 2023-02-27 · Closed 2023-09-29 · 88% similar
NETLOCK: Disclosed CRL is expired
#1962426 RESOLVED Incident Opened 2025-04-24 · Closed 2025-07-16 · 88% similar
NETLOCK: CA/Browser Forum TLS BR Non-compliance
#1979287 RESOLVED Incident Opened 2025-07-25 · Closed 2025-08-30 · 88% similar
NETLOCK: Expired Test Website Certificate
#2001327 RESOLVED Incident Revocation Issue Opened 2025-11-20 · Closed 2026-01-05 · 88% similar
NETLOCK: Missing CDP Disclosure in CCADB
#2007948 RESOLVED Self Reported Incident Incident Opened 2025-12-29 · Closed 2026-04-20 · 88% similar
NETLOCK: Full Incident Report was not published within 14 days of notification
#2011314 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Externally Reported Incident Opened 2026-01-19 · Closed 2026-06-23 · 88% similar
Netlock: unspecifed revocation code (0) in CRL

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action