As evidence, the lawsuit cites unnamed “courageous whistleblowers” who allege that WhatsApp and Meta employees can request to view a user’s messages through a simple process, thus bypassing the app’s end-to-end encryption. “A worker need only send a ‘task’ (i.e., request via Meta’s internal system) to a Meta engineer with an explanation that they need access to WhatsApp messages for their job,” the lawsuit claims. “The Meta engineering team will then grant access – often without any scrutiny at all – and the worker’s workstation will then have a new window or widget available that can pull up any WhatsApp user’s messages based on the user’s User ID number, which is unique to a user but identical across all Meta products.”
“Once the Meta worker has this access, they can read users’ messages by opening the widget; no separate decryption step is required,” the 51-page complaint adds. “The WhatsApp messages appear in widgets commingled with widgets containing messages from unencrypted sources. Messages appear almost as soon as they are communicated – essentially, in real-time. Moreover, access is unlimited in temporal scope, with Meta workers able to access messages from the time users first activated their accounts, including those messages users believe they have deleted.” The lawsuit does not provide any technical details to back up the rather sensational claims.
E2EE isn’t really relevant, when the “ends” have the functionality, to share data with Meta directly: as “reports”, “customer support”, “assistance” (Meta AI); where a UI element is the separation.
Yeah. E2EE isn’t a single open standard. It’s a general security concept / practice. There’s no way to argue that they don’t really have E2EE if in fact they do, but they keep a copy of the encryption key for themselves. Also, the workers client app can simply have the “decrypt step” done transparently. Or, a decrypted copy of the messages could be stored in a cache that the client app uses… who knows? E2EE being present or not isn’t really the main story here. It’s Meta’s obvious deceitful-ness by leveraging the implicit beliefs about E2EE held by us common folk.
Yeah, I guess if you want users to keep sharing “confessions, [] difficult debates, or silly inside jokes” through a platform you’ve acquired, E2EE might give the WhatsApp user the false sense of privacy required.
I don’t think it can be called End to End Encryption if it is actually End to End and The guy in the Middle.
Every technical definition of End to End Encryption states only the Sender and Recipient have keys to decrypt the message.
Anything else is using “End to End Encryption” purely as a marketing term like “Lite” or “Pure”.
It’s not End to End and The guy in the Middle. The message is encrypted from one end to the other. The detail about who has a copy of the key doesn’t spoil that fact, and I guarantee you Meta doesn’t care about using E2EE as a marketing term even if it misrepresents their actual product by matter of status quo. What matters is what they can theoretically argue in a court room.
A proper solution would be to have an open standard that specially calls out these details, along with certifications issued by trusted third parties.