3/ However it seems egregious of Ms Dick to raise this on the anniversary of a event which was clearly not enabled by E2E-Encryption - because there was hardly any of it in 2001.
Hell, the Paris attacks 14 years later, were arranged via plaintext SMS:
4/ The truth is that this is all part of a campaign to stop Facebook deploying E2E Encryption in (specifically) Facebook @messenger, the intention being to prove state power over encryption, and to dissuade innovation elsewhere:
6/ …and others are noting that @pritipatel is being awfully quiet about iMessage's existing end-to-end encryption whilst openly cheering Apple's privacy-disastrous on-device CSAM surveillance:
7/ So this is actually a "political game" - the world's governments want to hinder adoption of cryptography, and if they can visibly and embarrassingly stop Facebook — if they can MAKE AN EXAMPLE of Facebook — then (the thinking goes) they can stop anyone.
What happens then?
8/ If this happens, a massive chill will pass over the Internet:
Developers and startups will need to employ lawyers to tell them what code they may/may-not write.
Architectures which strongly protect data will be avoided, in favour of ones that speculatively support snooping.
9/ How do I know this? Because I lived through it in the 1990s. If you want to see lingering echoes of it, go look at this page:
10/ You needed a software "key" from the Java website, to be able to use cryptography in Java.
Export controls and other legal tools were employed by Governments to inhibit your ability to keep data safe, secure and private.
11/ The consequences echoed in security bugs for the next 20 years, with downgrade attacks and other weaknesses brought on by this obligatory nightmare.
Hot on the heels of #ChatControl and in the name of “identity” and “consumer choice” the EU seeks the ability to undetectably spy on HTTPS communication; 300+ experts say “no” to #Article45 of #eIDAS #QWAC alecmuffett.com/article/108139
If you would like to see more discussion regarding:
Regulation: EU Digital Identity Framework — including #eIDAS and #QWAC
When Signal and WhatsApp have fled the surveillance of the #OnlineSafetyBill, what app will still be around for politicans, journalists, and actual normal people to use, securely.
@JohnNaulty @matrixdotorg Let's be clear: we are talking about the evacuation of the entire Signal and WhatsApp userbase / niche, from the United Kingdom.
That's a lot of people.
WOW:
- No Signal
- No WhatsApp
- No iMessage
- No Facetime
@jamesrbuk called it #internexit; the UK will be extraordinarily isolated from the rest of the internet.
A big part of the the reason for the existence of that API was because the European Union wanted to enable people to access their data; so they created the problem, complained when the inevitable leaks happened, and are now reinventing it
Could be the attached, but my suspicion is that this is going to be another CYBER! DARKWEB! CYB3R! SYBER! CAMBRIDGE ANALYTICA‼️BRAIN CONTORL! YOU SAW AN ADVERT AND SO A RUSSIAN ARTIFISHIAL INTELLIGENCE APP MADE YOU VOTE FOR UKIP! … thing.
Plucky spooks in Cheltenham but dressed for speed-dating in 2015-era Shoreditch, battle "Russian influence operations" that Nadine Dorries will soon cite as rationale for the #OnlineSafetyBill.
Token American subplots help sell the series to the US.
Back in 1991 I published an open-source password cracking tool which defined the state of the art for the next 5+ years, so much so that echoes of it can be found in all major password crackers of today.
Some folk criticised me for doing this, choosing words like these to do so:
I know that in general it's bad form to take a single quote out of context and use it to critique an entire essay (concerned.tech) — but I do feel that this time it's deserved.
The concerned-dot-tech essay has had extensive technical debunking, e.g.: