Skip to content
NewA calmer, faster ZeroHour

Comodo AAA root trust removal unrelated to eMudhra

Original title: Re: eMudhra Intermediates Compromise

oss-security ()1
Part of a story covered by 7 sourcesBrowsers distrust eMudhra G3 root after weak intermediate keysMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Browsers dropped the TLS trust bit because the root, issued in 2004, exceeds the CA/Browser Forum's 15-year maximum lifespan.

In an oss-security reply, Jeffrey Walton says removal of the Comodo AAA Services Root TLS trust bit is not part of the eMudhra intermediates compromise. He says browsers removed the bit because the root is too old under current CA/Browser Baseline Requirements. Those rules cap a root at 15 years from creation, and this root was issued in 2004.

Unconfirmed: The post does not describe the eMudhra incident itself.

Key facts
  • Comodo AAA Services Root was issued in 2004.
  • Current CA/B Baseline Requirements limit roots to 15 years.
  • Walton says the trust-bit removal is unrelated to eMudhra.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

Posted by Jeffrey Walton on Oct 20 It is probably worth noting the Comodo AAA Services Root removal is not related to the eMudhra incident. The issue with Comodo AAA Services Root was the removal of the TLS trust bit by browsers because the root is too old. The current CA/Browser (CA/B) Baseline Requirements (BR) policies say a root has a maximum lifespan of 15 years from creation date.

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.