PGP, which hasn't fundamentally evolved since the 1990s, needs to die
What's the matter with PGP? — Last Thursday, Yahoo announced their plans to support end-to-end encryption using a fork of Google's end-to-end email extension. This is a Big Deal.
Context & Ripple Effects
This argument lands on top of two developments from the same summer: Google shipped its End-to-End Chrome extension alpha in June 2014, putting OpenPGP-based encryption inside a browser rather than a desktop client, and three days before this piece ran, Phil Zimmermann himself called out telco cooperation with governments while noting special forces already use his Silent Circle stack instead of classic PGP.
The news underneath the polemic is confirmed: Yahoo says it will support end-to-end email encryption by forking Google's End-to-End extension. If two of the largest webmail providers converge on the same codebase, the debate shifts from whether ordinary users get encrypted mail to which implementation replaces the PGP workflow the author calls frozen since the 1990s.
First-order effects
- Yahoo gets a shortcut to usable encrypted webmail — inheriting Google's extension work instead of building its own crypto stack — while Google's End-to-End code becomes a shared foundation across competing mail services.
Second-order effects
- Other consumer webmail providers come under pressure to offer comparable end-to-end options or concede 'secure email' as a differentiator to Yahoo and Google; the OpenPGP tooling ecosystem risks being bypassed if the big providers standardize on their own forked implementations.
Third-order effects
- If provider-integrated encryption scales where PGP never did, key management moves from hobbyist desktop software into browser extensions controlled by the platforms — and the PGP ecosystem's decades-long role as the default for personal email encryption erodes toward niche and legacy use.
The trend: Consumer email encryption is shifting from standalone PGP-era desktop tools to end-to-end schemes built into webmail itself, with large providers sharing and forking common codebases.