← Asseco Data Systems S.A. cases
Bugzilla #2030937 Dedicated Root Transition

Asseco Data Systems (Certum): Transition Plan for Existing Dual-Purpose Roots

ASSIGNED Asseco Data Systems S.A.
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

Asseco Data Systems (Certum) submitted a refined transition plan for its multi-purpose (TLS and S/MIME) root generations. The plan describes moving from existing multi-purpose roots (G1 and G2) to a single-purpose G3 hierarchy, with migration phased to align with acceptance of the G3 roots into relevant root programs. Certum stated it will migrate TLS issuance to G3 and use cross-certified trust paths from G1/G2 to the new G3 roots while G3 roots await wider inclusion, and it will cease TLS issuance from multi-purpose roots once migration is complete. For S/MIME, Certum stated that issuance will be transitioned to G3 and that multi-purpose roots will cease S/MIME issuance after the proposed completion steps, while noting that ~20,000 valid certificates remain under G1/G2 for S/MIME. The plan includes proposed distrust dates for the Websites trust bit for certain TLS roots and proposed distrust dates for S/MIME after dates for specific generations. Certum also stated it does not plan to proactively revoke existing SubCAs issued from G1 or G2, and that these SubCAs will remain active until their natural expiration to avoid service disruptions.

Model: gpt-5.4-nano Generated: 2026-06-13 21:37 UTC Revised: 2026-06-16 18:15 UTC Confidence: 0.90 1 comment
Chronology
  1. Certum/Asseco DS submitted a refined transition plan to move from multi-purpose G1/G2 roots to single-purpose G3 roots for TLS and S/MIME.
  2. Mozilla assigned the case to Ben Wilson.
Thread Activity
  1. Assecods representative — Submitted the refined transition plan detailing affected roots, proposed migration approach for TLS and S/MIME, proposed distrust_after_date values, and stated it would not proactively revoke existing SubCAs from G1/G2.
Participants
Assecods representative Mozilla representative
Similar Local Cases
#2018979 ASSIGNED Remediation Tracking Self Reported Incident Opened 2026-02-24 Still Open · 72% similar
eMudhra: Transition Plan for Existing Dual-Purpose Roots
#2031867 ASSIGNED Dedicated Root Transition Opened 2026-04-14 Still Open · 62% similar
Identrust: Transition Plan for Existing Dual-Purpose Roots
#2020140 ASSIGNED Dedicated Root Transition Root Lifecycle Opened 2026-02-28 Still Open · 62% similar
HARICA: Transition Plan for Existing Dual-Purpose Roots
#2032053 ASSIGNED Dedicated Root Transition Opened 2026-04-15 Still Open · 61% similar
GlobalSign: Transition Plan for Existing Dual-Purpose Roots
#2030950 ASSIGNED Dedicated Root Transition Opened 2026-04-10 Still Open · 61% similar
KIR SA: Transition Plan for Existing Dual-Purpose Roots
#2026208 ASSIGNED Dedicated Root Transition Opened 2026-03-25 Still Open · 60% similar
Telekom Security: Transition Plan for Existing Dual-Purpose Roots
#2017182 ASSIGNED Dedicated Root Transition Opened 2026-02-16 Still Open · 60% similar
Sectigo: Transition Plan for Existing Dual-Purpose Roots
#2032100 ASSIGNED Dedicated Root Transition Opened 2026-04-15 Still Open · 60% similar
SECOM: Transition Plan for Existing Dual-Purpose Roots

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

Confirm action