DIFF.BLOG
New Following Discover Jobs
More
Top Writers Suggest a blog Upvotes plugin
Report bug Contact About Privacy
Sign up
Topics
Follow your own topics →
Menu
New Following Discover Jobs Top Writers
More
Suggest a blog Upvotes plugin Report bug Contact About
Sign up
Privacy Policy
The home for great developer writing.
We surface the best developer writing from thousands of independent blogs, updated daily.
Join Diff.blog
TOPICS

End-to-End Encryption and “Going Dark”

· Bruce Schneier · July 23, 2026, 11:05 a.m.
Academic Papers Backdoors crypto wars Encryption data-privacy end-to-end encryption surveillance
Summary
This blog post by Bruce Schneier discusses the evolving debate over End-to-End Encryption (E2EE) and its implications for law enforcement and national security. It analyzes the historical context of the 'Going Dark' debate in three rounds, from the Crypto Wars of the 1990s to current controversies surrounding E2EE, exploring the balance between privacy and security.
Read full post on www.schneier.com →
MORE POSTS LIKE THIS
ICE Is Buying Access to Credit Card Records
Bruce Schneier · Aug 7, 2026
data-privacy surveillance
Westchester Drivers Challenge County Police Department’s Warrantless Mass Vehicle Surveillance System
Knightcolumbia · Jun 9, 2026
privacy surveillance
Hey, built my first actix-web middleware crate and would love some feedback, especially on the crypto layer
Users Rust Lang · Apr 26, 2026
Middleware Cryptography
What I Found Trying to Build FHE from One-Time Pads
MiscellaneousStuff · Mar 27, 2026
fully homomorphic encryption project
Introducing NVIDIA cuPQC for GPU-Accelerated Post-Quantum Cryptography
NVIDIA Corporation · Dec 3, 2024
Cybersecurity Simulation / Modeling / Design
Introducing AlphaProof Code: a breakthrough in verifying complex software at depth
DeepMind · Nov 10, 2026
Encryption software development
Discover more posts →
AUTHOR
BLOG POST FEATURED ON

Placeholder image
Hacker News

4 points

Add this plugin to your blog
RECENT POSTS FROM THE AUTHOR
Choose how you want to continue.
Continue with GitHub Continue with Google
By continuing, you agree to our Privacy Policy.