Calling it now: Chrome and Mozilla will remove eMudhra as a G1 root, nulling them as a CA. On 20 Oct, eMudhra had 24 hours to give an explanation of what exactly happened with the mis-signed certificate. They did not; asked for more time; and now blame “investors/customers” 🤡Read original on X
StoryFirst seen
Chrome and Mozilla plan to drop eMudhra as trusted certificate authority
Removing a certificate authority from browser trust lists can block its certificates across the web.
Everything it touches
0 names 1 voices 2 source posts
The story’s neighborhood
Explore the graph, or choose a connection below.
Follow the evidence
The source posts
This brief comes from Tech Twitter’s edited headlines. The posts below are the sources grouped with the story; statements in them belong to their authors.
I want to see answers, because eMudhra’s explanation of how they mis-generated the private key for a certificate doesn’t add up. It also doesn’t add up how they claim the process was faulty one day; but not the next; and they did nothing about it for 1.5 years (???)Read original on X
How the headline evolved
Chrome and Mozilla plan to drop eMudhra as trusted certificate authority
Chrome and Mozilla plan to drop eMudhra as a trusted certificate authority
Chrome and Mozilla to drop eMudhra as trusted certificate authority
Chrome and Mozilla to drop eMudhra as trusted certificate authority
Chrome and Mozilla to drop eMudhra as trusted certificate authority
Chrome and Mozilla plan to drop eMudhra as trusted certificate authority
Chrome and Mozilla plan to drop eMudhra as trusted certificate authority
Chrome and Mozilla move to drop eMudhra as trusted certificate authority
Chrome and Mozilla move to drop eMudhra as trusted certificate authority
Chrome and Mozilla move to drop eMudhra as trusted authority
Chrome and Mozilla move to drop eMudhra as a trusted certificate authority
Chrome and Mozilla move to drop eMudhra as a trusted certificate authority
Chrome and Mozilla likely to drop eMudhra as trusted certificate authority