this post was submitted on 28 Jan 2026
199 points (99.5% liked)
Privacy
45284 readers
418 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Correct, WhatsApp fails to include a libre software license text file. We do not control it. So, it has never been secure.
Being FOSS is not a prerequisite of E2EE but a prerequisite of knowing it's E2EE for sure. Like, I can give you a black box that prints PGP key pairs and says "includes RPGP, MIT-licensed PGP library" but you can't trust that the machine doesn't use modified, low-entropy RNG or exfiltrate the results. The communication you do with these PGP keys is technically E2EE − a third party server relaying your messages will not be able to read them, unless I provide them with the potentially not-so-secret "random" data my box generated.
But you're right: if my black boxes are also used to encrypt/decrypt the messages with "your" keys (made by them) and I run a non-transparent ssrvice that delivers the messages, there is a case for not calling it E2EE.