#WebPKI
Rust TLS devs surfaced detection of the leaked #eMudhra intermediates so we surfaced it all the way up to the customer's SIEM, in case their #egress firewall was misconfigured or diverted with spoofing. It's 'CertDistrusted' in the rustls-webpki library: docs.rs/rustls-webpk...
November 11, 2026 at 3:57 PM
Every time your browser negotiates a TLS handshake, we tell ourselves a comforting story about mathematics. But WebPKI is not an algorithmic triumph—it is a fragile, human-run geopolitical cartel.
The Illusion of Identity: Why WebPKI is a Geopolitical Truce, Not Cryptography
Every time your browser negotiates a TLS handshake and illuminates a lock icon in the address bar, an unspoken theological assumption is validated. We tell ourselves a comforting story about mathematics: that discrete logarithms, elliptic curves, and 2048-bit RSA keys protect us from an adversarial world. The math, to be fair, is flawless. No nation-state or rogue actor is factorizing 256-bit prime curves in polynomial time. Yet our reliance on this mathematical perfection obscures a far more precarious reality: the cryptography is merely the decorative paint on a rickety, human-run political institution. The real architecture of internet security—the Web Public Key Infrastructure (WebPKI)—is not an algorithmic triumph. It is a fragile, de facto geopolitical cartel. It operates less like a software standard and more like 17th-century maritime law: a series of reluctant armistices between sovereign states, profit-seeking corporate intermediaries, and an oligopoly of Silicon Valley browser vendors acting as judge, jury, and executioner. And now, as generative AI collides with automated identity verification, the paper-thin boundary between cryptographic proof and legal entity authentication is starting to fracture. * * * ### The Physical State vs. The Digital Frontier In the physical world, identity authentication is a recognized public good—and almost universally a sovereign monopoly. If you want to prove who you are, the state assigns you a birth certificate, a Social Security number, or a driver’s license. If you want to incorporate an entity, you petition a secretary of state. The state bears the overhead of enforcing identity because fraud introduces severe market externalities. When the commercial web exploded in the 1990s, the physical state was structurally incapable of assuming this role online. Territorial sovereignty stopped at the router. A German browser could not rely on a Chinese ministry or an American bureau to vouch for the cryptographic identity of a banking server hosted in Iceland. Furthermore, governments were—and remain—untrusted adversaries. A state-run global PKI would have granted intelligence agencies native root authority to issue arbitrary interception certificates against foreign nationals. So, the web privatized the production of trust. Into this vacuum stepped Certificate Authorities (CAs)—commercial enterprises whose sole business model was to sell trust. If you paid VeriSign, Sectigo, or DigiCert a recurring fee, they promised to verify that you owned your domain and sign your public key with their coveted root certificate. This created an immediate, fatal economic contradiction: a race to the bottom. * * * ### The CA Cartel and the Lemons Problem In economic terms, digital certificates suffer from a classic market for lemons. A browser does not reward a Certificate Authority for running exhaustive background checks on a customer. A mathematical certificate signed with grueling, meticulous verification looks identical to a certificate rubber-stamped after a five-minute ping test. Because CAs were profit-seeking firms competing on price and speed, their economic incentive was not to be rigorous; it was to issue as many certificates as humanly possible with the lowest operational overhead. The consequences were predictable: * In 2011, Dutch CA DigiNotar was breached, resulting in fraudulent certificates issued for *.google.com used to intercept Iranian dissidents. * In 2015, Symantec was caught issuing rogue certificates for domains like Google without authorization, kicking off a multi-year audit that eventually ended in Google and Mozilla forcibly distrusting Symantec's entire root empire. * Rogue intermediate CAs and compromised regional registrars repeatedly demonstrated that the chain of trust was only as strong as the most corruptible, least secure CA in the global root store. If WebPKI were purely a market, the market would have collapsed under the weight of its own fraud. What prevented total failure was not the market, nor a government regulator. It was a corporate coup. * * * ### The Sovereign Browsers: Unilateralism as Law The governing body of this ecosystem is nominally the CA/Browser Forum (CA/B Forum)—a consortium of browser vendors and CAs designed to negotiate baseline requirements. In reality, the CA/B Forum is a theater of consensus. Real power resides exclusively with the entities that curate the local root stores: Apple, Microsoft, Mozilla, and overwhelmingly, Google Chrome. Your operating system and your browser ship with a hardcoded list of roughly 150 trusted root certificates. If your root certificate is in that list, you can vouch for any server on planet earth. If you are removed from that list, your commercial business ceases to exist overnight. When Certificate Authorities dug their heels in against reforms that threatened their bottom lines, the browser vendors stopped negotiating: 1. **Certificate Transparency (CT):** When CAs resisted public accountability, Google mandated that any certificate not logged to public, append-only cryptographic logs would simply trigger an invalid security warning in Chrome. The CAs folded. 2. **Shortened Lifespans:** When CAs repeatedly voted down proposals in the CA/B Forum to reduce certificate validity from two years to one year (and eventually down to 90 days), Apple unilaterally announced at a conference that Safari would reject two-year certificates. Google and Mozilla followed. The forum vote was moot. WebPKI is not a democracy. It is an enforced corporate oligopoly. A browser’s rendering engine is the ultimate regulatory tribunal. * * * ### The ACME Shift and the Collapse of Identity To solve the lemons problem and eliminate commercial friction, the internet embraced automation. The advent of Let’s Encrypt and the ACME protocol (Automated Certificate Management Environment) transformed HTTPS from an expensive enterprise ritual into an automated HTTP-01/DNS-01 challenge. Over 85% of the web is now encrypted. It was a triumph for privacy against passive eavesdropping. But it subtly obliterated the concept of identity. A modern Domain Validated (DV) certificate does not verify who you are. It only proves that the entity requesting the certificate has control over a DNS record or an HTTP endpoint at that exact second. For years, the legacy CA industry tried to market Extended Validation (EV)—the green bar in the browser that displayed the verified corporate name. The promise was that manual human compliance officers had combed through legal registries, verifying that Bank of America was actually Bank of America. Browsers quietly killed the green bar years ago. Users did not understand it, attackers spoofed it, and human compliance verification was notoriously easy to social-engineer. * * * ### The Generative Threat: Smashing the Validation Boundary This brings us to our current frontier. The technical architecture of WebPKI was designed under the assumption that identity theft requires either cryptographic factorization, network interception (mitigated by BGP monitoring and DNSSEC), or deliberate human corruption. Generative AI dismantles the human validation boundary entirely. Consider the reality of how domain registration, business verification, and identity checks operate today: * Generating synthetic corporate filings, convincing articles of incorporation, fabricated utility bills, and spoofed officer identities used to require seasoned white-collar fraudsters. LLMs and deepfake pipelines have driven the marginal cost of this infrastructure to zero. * Autonomous agent frameworks can spin up disposable LLCs, buy aging domains, build rich digital histories, and systematically petition registrar and verification APIs at scale without a single human finger touching a keyboard. * If identity verification retreats to automated verification pipelines, we enter an adversarial machine-learning arms race where the verifier is a static parser and the attacker is an iterative optimizer. When an AI agent can mimic legal legitimacy perfectly, identity verification ceases to be an authentication mechanism. It becomes noise. * * * ### The Geopolitical Horizon Where does this leave us? As sovereign states wake up to the fact that four American tech companies control the global trust anchor of the internet, the pressure to fragment WebPKI along geopolitical fault lines is escalating. Authoritarian regimes have repeatedly attempted to mandate state-controlled root certificates within their borders. The European Union’s push under eIDAS 2.0 (Article 45) to force browser vendors to trust government-issued Qualified Website Authentication Certificates (QWACs) without the right to revoke them is the clearest warning sign yet: governments are tired of being regulated by Google and Apple. If the sovereign state takes back the root store, the global WebPKI collapses into regionalized state surveillance. If the browser oligopoly maintains control, we preserve technical integrity at the cost of corporate absolutism—while watching our identity frameworks get dismantled by synthetic intelligence. The green lock was never a badge of truth. It was a treaty between corporations who couldn’t afford to let the internet burn and browsers powerful enough to enforce the peace. As that treaty begins to fray under the weight of geopolitical division and synthetic reality, we are about to find out what happens when the math is the only thing we have left.
www.howonplanetearth.com
November 15, 2026 at 11:36 PM
I'm unfamiliar with webtiles in the webPKI ecosystem unfortunately
November 7, 2026 at 7:42 PM
For the in-person payments world, PCI PIN auditors examine key handling procedures and ceremonies. It isn't perfect, but staggering how nothing like this exists in the WebPKI world for CAs that the entire Internet depends…

— from @dinodaizovi (https://x.com/dinodaizovi/status/2120410403243216934)
November 11, 2026 at 7:11 AM
On Monday, Microsoft removes eMudhra's RSA root from Windows and Edge.

It's the root InCommon told universities to move to 3 weeks ago. 58% of those SSL certificates haven't been replaced yet.

www.certkit.io/blog/emudhra...

#WebPKI #InCommon
eMudhra's RSA root is distrusted too, and InCommon schools have to move again
Microsoft removes emSign Root CA - G1 on November 16, so InCommon schools that moved to eMudhra's RSA root replace every certificate again.
www.certkit.io
November 13, 2026 at 1:50 PM
chiming here from the @foryou.club feed via @anisota.net: is atproto implementation of webtiles similar to those within the WebPKI ecosystem?

also doing a quick read in case
November 7, 2026 at 12:42 PM
To see whether a Rust binary has the eMudhra key blocklist, run cargo tree -i rustls-webpki. 0.103.16 (2026-10-20) has it; 0.102.x, used by rustls 0.23.23 and older, never got it.
October 29, 2026 at 10:32 AM
On macOS, rustls with OS roots (rustls-native-certs) accepted the eMudhra test servers until rustls-webpki 0.103.16. reqwest 0.13 defaults and native-tls rejected them via Apple's revocation.

https://importstatic.com/rust/rustls-emudhra-distrust
Which Rust TLS setups trusted the compromised eMudhra certificates
On macOS, rustls with OS roots accepted the eMudhra test servers until rustls-webpki 0.103.16. Apple-verified setups rejected them; cargo update fixes the rest.
importstatic.com
October 29, 2026 at 7:10 AM
Gram 3.4.0 출시, eMudhra 인증서 보안 수정과 Git 좌우 비교 뷰 추가

Gram에 포함된 인증서 관련 패키지가 eMudhra CA 문제 의 영향을 받아 보안 수정 버전을 출시함. 가능한 한 빨리 3.4.0으로 업그레이드하거나, 기존 버전의 소스를 최신 webpki 패키지로 다시 빌드할 것을 권고함 Git diff 좌우 비교 뷰 와 Git 패널에서 접근할 수 있...
Gram 3.4.0 출시, eMudhra 인증서 보안 수정과 Git 좌우 비교 뷰 추가
Gram에 포함된 인증서 관련 패키지가 eMudhra CA 문제 의 영향을 받아 보안 수정 버전을 출시함. 가능한 한 빨리 3.4.0으로 업그레이드하거나, 기존 버전의 소스를 최신 webpki 패키지로 다시 빌드할 것을 권고함 Git diff 좌우 비교 뷰 와 Git 패널에서 접근할 수 있...
news.hada.io
October 27, 2026 at 1:00 AM
The release addresses a critical vulnerability caused by shipping outdated webpki-roots packages. New features include a side-by-side Git diff view and other improvements.

#Gram #Rust #Security
Gram released editor version 3.4.0
Source: Lobsters
realfeedapp.com
October 26, 2026 at 6:02 PM
あのWebPKIの実際のところPHPより影響がでかいやつ、それを起こした認証局がGoogleに永遠に言い訳と反論を続けてて野次馬するぶんにはおもろい 野次馬するぶんには
https://bugzilla.mozilla.org/show_bug.cgi?id=2083449#c43
October 26, 2026 at 1:12 AM
[Backport release-26.05] autocorrect: update webpki-roots

https://github.com/NixOS/nixpkgs/pull/578468

#security
October 25, 2026 at 12:22 AM
[Backport release-26.05] shadow-tls: update webpki-roots

https://github.com/NixOS/nixpkgs/pull/578466

#security
October 25, 2026 at 12:22 AM
October 24, 2026 at 8:06 PM
October 24, 2026 at 7:33 PM
October 23, 2026 at 8:38 PM
So eMudhra is exiting the webpki business because the scrutiny they got was out of proportion. you affect the entire internet so your practices should be to a global standard. but also, they still have a large domestic digital signing business which might also be irresponsibly run
October 22, 2026 at 4:20 PM
[Backport release-26.05] dprint: cherry-pick webpki-roots 0.26.7 -> 1.0.10

https://github.com/NixOS/nixpkgs/pull/577636

#security
October 23, 2026 at 2:39 PM
it legitimately got me interested in webPKI, seeing the scale of the massive regulatory capture resulting in the normalisation of deviance
October 22, 2026 at 8:04 AM
Rustup 1.29.2 has been released.

This is a small release which only updates the rustls-webpki and webpki-root-certs dependencies to remove the compromised eMudhra intermediate certificates.

See the announcement for details: blog.rust-lang.org/2026/10/20/R...
Announcing rustup 1.29.2 | Rust Blog
Empowering everyone to build reliable and efficient software.
blog.rust-lang.org
October 21, 2026 at 12:29 PM
On mobile, I accidentally typo'd "dumpster fire" as "dumbster fire" and now I have a new way to describe unresolved WebPKI issues.
October 21, 2026 at 5:30 PM
October 22, 2026 at 3:41 AM
The unresolved issue is the WebPKI trust model itself: eMudhra is leaving, but the audit ecosystem that approved them is unchanged. Commenters were left asking how many other trusted root CAs are passing compliance reviews on paper while running broken crypto behind the scenes. 4/4
October 22, 2026 at 7:00 PM