this post was submitted on 27 Jan 2026
1269 points (99.6% liked)
Technology
79576 readers
4417 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Even if that's all true, it's not evidence that the end to end encryption is broken.
That sort of debug access could simply be included in the clients.
I'm not sure if it's the encryption part you don't understand, the end to end, or both.
I understand perfectly well, it's you who doesn't.
If the illegitimate access happens on the client which is the endpoint of the e2e-encryption then it doesn't say anything about the e2e-encryption working or not working. On the endpoint the content is always available decrypted, for user consumption
Ah, so you don't understand what the word user means. Got it.
an end to end encryption implementation is broken when secret keys leak, whether its intentional or not.
Nowhere in the given scenario do secret keys leak.
The "encryption for two different receiving sides" part is the one that you, in turn, might have missed. WhatsApp client might just send messages to some additional technical party, which is not your buddy.