Tech
Disgraced eMudhra drops out of TLS business after using cert private key of 4
Publication: Ars Technica - All content
Author: Dan Goodin
Source published: 22/10/2026, 20:17:52 UTC
Briefing created: 23/10/2026, 00:44:39 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 23/10/2026, 00:28:24 UTC.
Briefings
eMudhra, an Indian certificate authority, announced it is withdrawing from the global SSL/TLS business after issuing eight intermediate credentials containing weak encryption keys, including one with a private key of just 4. Chairman V. Srinivasan attributed the decision to rising compliance costs, operational complexities, and the company's low revenue share of 1 percent, alongside increased competition from free certificate providers.
Key points
- eMudhra issued eight intermediate TLS credentials with weak encryption, including one with a private key of just 4.
- Chairman V. Srinivasan cited increasing compliance costs and low revenue share of 1 percent as reasons for withdrawal.
Context
eMudhra, an Indian certificate authority, announced it is withdrawing from the global SSL/TLS business after issuing eight intermediate credentials containing weak encryption keys, including one with a private key of just 4. Chairman V. Srinivasan attributed the decision to rising compliance costs, operational complexities, and the company's low revenue share of 1 percent, alongside increased competition from free certificate providers.
Limitations
Evidence is limited to the company's internal statement from October 2026 regarding the withdrawal decision. Specific financial figures for the 1 percent revenue share are provided, but broader market data on free certificate providers or the impact of the weak keys on the industry is not supplied. The article does not contain external validation of the key weakness or the company's future plans.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 23/10/2026, 00:44:39 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeic3inghm33axzmwtr3ag62fl7i7fqerzzwvymyg4hvgup5tbknt3e