4 ms·
> if it did and Facebook complied, it would disprove their claim that e2e encryption as they use it provides sufficient privacy You made me envision this "end-
by thaumasiotes 5y ago
> if it did and Facebook complied, it would disprove their claim that e2e encryption as they use it provides sufficient privacy
You made me envision this "end-to-end encryption" scheme:
- Alice sends a message to Bob. True to its word, WhatsApp encrypts the message on Alice's client and transmits it through to Bob without the WhatsApp server ever being able to read the message.
- Bob receives the message, which is decrypted for his viewing by his WhatsApp client.
- Bob's WhatsApp client reads the message and reports it back to the WhatsApp server.
- henearkr 5y agoExactly. So e2e makes sense only when the client is open source too. Signal got this right.
- cantrevealname 5y ago> Bob's WhatsApp client reads the message and reports it back to the WhatsApp server. In every copy of the app, WhatsApp explicitly says, "Your messages, calls and status updates stay between you and the people you choose. Not even WhatsApp can read or listen to them." Of course, the scenario you describe is possible, but WhatsApp would be lying.
- dTal 5y ago>Not even WhatsApp can read or listen to them WhatsApp is already lying. It can, as demonstrated above.
- WhyNotHugo 5y agoWhatsApp's TOS uses to state that the encryption key stays on device. This changed a few months ago.
- PeterisP 5y agoA lawyer could argue that sending a hash of the transmitted file (or, preferably, locally verifying the hash against a blacklist) is substantially different from sending/reading its contents.