← LuxTrust cases
Bugzilla #1060863 Remediation Tracking

LuxTrust: issuing 1024 bit certificates

RESOLVED FIXED LuxTrust
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 involves LuxTrust's issuance of 1024-bit certificates, which are in violation of CA/B Forum Baseline Requirements. The issue was initially raised by Kurt Roeckx, who reported seeing recent 1024-bit certificates issued under the LuxTrust root CA. LuxTrust acknowledged the problem and confirmed that the last 1024-bit certificate was issued in July 2011, but subsequent comments revealed that several 1024-bit certificates were issued after this date. LuxTrust committed to replacing the remaining active 1024-bit certificates with 2048-bit certificates by the end of the year. The bug was ultimately resolved as LuxTrust took corrective actions and confirmed that the issue was addressed.

Model: gpt-4o-mini Generated: 2026-06-13 13:59 UTC Revised: 2026-06-16 19:09 UTC Confidence: 0.85 18 comments
Chronology
  1. Initial report of 1024-bit certificates issued by LuxTrust.
  2. LuxTrust initiated an assessment of the situation regarding the 1024-bit certificates.
  3. LuxTrust confirmed plans to replace active 1024-bit certificates with 2048-bit certificates.
  4. LuxTrust confirmed that identified 1024-bit certificates had been revoked.
  5. LuxTrust confirmed that the bug report could be closed.
Thread Activity
  1. Roeckx representative — Reported seeing recent 1024-bit certificates from LuxTrust.
  2. Luxtrust representative — Clarified that the 1024-bit certificates were issued under a CA not in the scope of their submission.
  3. Luxtrust representative — Initiated an in-depth assessment of the situation regarding the 1024-bit certificates.
  4. Luxtrust representative — Provided outputs of the assessment and confirmed plans to replace 1024-bit certificates.
  5. Luxtrust representative — Confirmed that the bug report can be closed.
Participants
Community commenter Luxtrust representative Ian representative Mozilla representative
External References
Similar Local Cases
#1566580 RESOLVED Ca Documents Remediation Tracking Opened 2019-07-16 · Closed 2022-11-14 · 65% similar
LuxTrust: Overdue Audit Statements 2019
#1738778 RESOLVED Ca Certificate Compliance Incident Remediation Tracking Opened 2021-11-01 · Closed 2023-02-22 · 61% similar
TWCA: Policy OID not set to indicate the assurance level to the issued certs
#1848306 RESOLVED Ca Certificate Compliance Certificate Misissuance Remediation Tracking Opened 2023-08-11 · Closed 2023-11-02 · 60% similar
TWCA: CA certificate without EKU
#1578505 RESOLVED Self Reported Incident Opened 2019-09-03 · Closed 2024-06-30 · 60% similar
LuxTrust: Outdated audit statement for intermediate certificate
#1793445 RESOLVED Ca Security Vulnerability Remediation Tracking Opened 2022-10-03 · Closed 2023-04-19 · 59% similar
TWCA: "unknown" OCSP response for issued certificates
#1848240 RESOLVED Ca Certificate Compliance Incident Remediation Tracking Opened 2023-08-10 · Closed 2023-11-02 · 59% similar
TWCA: Undisclosed CA
#1651026 RESOLVED Certificate Misissuance Incident Remediation Tracking Opened 2020-07-07 · Closed 2023-02-22 · 59% similar
Izenpe: certificate issued to internal domain
#1802916 RESOLVED Ca Certificate Compliance Certificate Misissuance Remediation Tracking Opened 2022-11-28 · Closed 2023-04-24 · 58% similar
Entrust: EV TLS Certificate incorrect jurisdiction

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

Confirm action