this post was submitted on 27 Jan 2026
833 points (99.6% liked)
Technology
79355 readers
4240 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
I don't agree that would fit the protocol of end to end, that's a common misconception, E2E by design means that it's encrypted from the sender to the intended recipient. When you send a message the intended recipient isn't the server, it's the user you are sending to. That type of system would be called an encrypt in transit or a server client encryption not E2E. If they are classifying it as E2E that would be incorrect.
A classic example of a server client or encrypt in transit would be HTTPS, the server acts as a middleman between the clients, meaning that it decrypts the message then re-encrypts the message to the designated choice.
With an e2e system, the message the server transmits is never decrypted, the server already knows the destination based off the public key
Except it is still encrypted to the intended recipient. As the other commenter said, WhatsApp is just another "member" of the group that you can't see. Basically all they'd have to do is have a server somewhere functioning as a WhatsApp client. Your client sends the message to your intended recipient. It also then sends the message to their "client." The routing server for the messages can't decrypt the messages. All the messages are still encrypted per-member of the group and can't be decrypted until it hits the ends, but WhatsApp is basically a mole siphoning all your messages and storing them.
An e2ee group chat would need every member to have every other member's public key. So for 5 people, your client would sign with your private key and send 4 unique messages encrypted each with 1 other person's public key. Each of them would decrypt their copy of the message with their private key and verify the signature with your public key. So I think what arcterus was saying was that employee who requests access to a user's messages then becomes just another member of a group chat, but the UI just doesn't show it as such. Every message you send is then secretly encrypted, on your client, with their special public key and sent to them to be decrypted. That would still be E2EE.
ok yea, I do agree with that POV on it. A ghost key like that would be within spec, cause yea at that point it would just be another member. I wasn't taking it as an additional group member though, since the whistleblower is stating that they can put in any user id and have access to all messages live, that would mean they would have a ghost user on all messages period regardless of if its a group chat or not.
That wouldn't be implausible though.
I will say, not too long ago there was some question if I had setup a WhatsApp account with my number due to some emails I was receiving. Not wanting to install the app and unwittingly create an account just by checking if I had one, my wife created a group chat with just her and my number, sent a message, and then we saw it get marked as read by all. Which in an E2EE system should not have been possible without me having the app setup. so I did go ahead and wiped an old and setup the app to make sure I was in control of any account for my number, and I did then receive that group chat. But still, very sketchy.