this post was submitted on 06 Mar 2024
320 points (87.2% liked)
Privacy
32492 readers
337 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 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What happened with Telegram? I'm unfamiliar with those particular rumors.
... But also definitely not a fan of it in general. Their app has had terrible encryption (when it's even used) for a long time.
There have been rumors from its start. I have no idea of their validity. Like anything, it's hard to find the truth.
As for its encryption, while I dislike it's not open source, and it's deserving of some criticism, there have been no reported cracks of it that I'm aware.
That said, it seems to store your ~~public~~ private key on the server (though I'm not sure of this), which is not ideal, for sure.
The "no reported cracks" thing is a red herring. You can make an intentionally broken cryptography system and claim it's unbroken too.
And even if it was sound, it doesn't really matter because the messages are decrypted by the server for all desktop and group chats, and probably most one-on-one chats too.
There has been multiple breaks, like the good old 2^64 bruteforce attack when they used too short session identifiers, malleability issues that could let the server/hackers change your messages, reordering attacks, etc.
What the issue with them storing the public key?
Aside from not storing anything you don't absolutely need to store, there shouldn't be an issue there.
Typo