← Sectigo cases
Bugzilla #2017182 Dedicated Root Transition

Sectigo: Transition Plan for Existing Dual-Purpose Roots

ASSIGNED Sectigo
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 documents Sectigo’s transition plan to migrate its existing dual-purpose roots to S/MIME-only trust before 2029, pursuant to section 7.5.3 of the Mozilla Root Store Policy. The trigger for the transition is that, according to Mozilla’s Root CA Lifecycle Transition Schedule, the Websites trust bit for all but one of Sectigo’s dual-purpose roots was due to be removed before 2029 due to the age of their key generation dates. Mozilla acknowledged receipt of Sectigo’s plan and stated it would proceed with an NSS bug to remove the Websites trust bit for three specific root CA certificates: COMODO Certification Authority, Entrust Root Certification Authority – G2, and Entrust Root Certification Authority – EC1. Mozilla also stated that removing the Websites trust bit would transition these roots to S/MIME-only trust, with further trust bit removals for the remaining dual-purpose roots handled according to the published schedule. On 2026-04-15, the CA Program reported that in NSS 3.123 and Firefox 151 the Websites trust bit was removed from those three root CA certificates and that CCADB records were updated accordingly. The bug remains in ASSIGNED status.

Model: gpt-5.4-nano Generated: 2026-06-13 20:55 UTC Revised: 2026-06-16 19:05 UTC Confidence: 0.90 3 comments
Chronology
  1. Sectigo submitted a transition plan to migrate dual-purpose roots to S/MIME-only trust before 2029.
  2. Mozilla acknowledged the plan and indicated it would remove the Websites trust bit for three specified roots via an NSS change.
  3. Mozilla removed the Websites trust bit for the three specified roots in NSS 3.123/Firefox 151 and updated CCADB records.
Thread Activity
  1. Sectigo — Rob Stradling provided Sectigo’s transition plan for migrating dual-purpose roots to S/MIME-only before 2029 and requested removal of the Websites trust bit from the Entrust G2 and EC1 roots at the earliest convenience.
  2. Mozilla representative — Ben Wilson acknowledged receipt of the plan and said Mozilla would proceed with an NSS bug to remove the Websites trust bit for COMODO, Entrust G2, and Entrust EC1, transitioning them to S/MIME-only trust.
  3. Mozilla representative — Ben Wilson reported that in NSS 3.123 and Firefox 151 the Websites trust bit was removed from COMODO, Entrust G2, and Entrust EC1, and that CCADB records were updated accordingly.
Participants
Sectigo Mozilla representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2032100 ASSIGNED Dedicated Root Transition Opened 2026-04-15 Still Open · 69% similar
SECOM: Transition Plan for Existing Dual-Purpose Roots
#2020150 ASSIGNED Dedicated Root Transition Opened 2026-02-28 Still Open · 69% similar
Telia: Transition Plan for Existing Dual-Purpose Roots
#2018158 ASSIGNED Dedicated Root Transition Operational Change Opened 2026-02-20 Still Open · 69% similar
OISTE: Transition Plan for Existing Dual-Purpose Root
#2017381 ASSIGNED Dedicated Root Transition Opened 2026-02-17 Still Open · 68% similar
TWCA: Transition Plan for Existing Dual-Purpose Roots
#2032060 ASSIGNED Dedicated Root Transition Opened 2026-04-15 Still Open · 68% similar
Microsec: Transition Plan for Existing Dual-Purpose Roots
#2032053 ASSIGNED Dedicated Root Transition Opened 2026-04-15 Still Open · 67% similar
GlobalSign: Transition Plan for Existing Dual-Purpose Roots
#2030950 ASSIGNED Dedicated Root Transition Opened 2026-04-10 Still Open · 67% similar
KIR SA: Transition Plan for Existing Dual-Purpose Roots
#2020140 ASSIGNED Dedicated Root Transition Root Lifecycle Opened 2026-02-28 Still Open · 67% similar
HARICA: 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