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.
You gatta be real stupid to not realize that Facebook is harvesting your data.
No surprised at all tbf.
I never used WhatsApp, but what made people think they used e2e? I’m way passed blindly believing what any company says they do without proof. I’d expect some kind of key or certificate management in the app, is that present?
Heck… my default is still to think every website does plaintext password storage. I can’t prove it, but neither can they. Stop storing my passwords in plaintext lemmy! /s
Back at the start WhatsApp wasn’t free, although it was pretty cheap. Then Meta bought it and made it free. Some time after that, the founders left and started Signal.
The E2E encrypted protocol WhatsApp used to use was the Signal protocol. When the OG founders left and created Signal they revamped it, calling it the Signal V2 protocol. Whether WhatsApp still uses that original Signal protocol or not is probably not known to many people outside of Meta, but WhatsApp definitely used to be E2E encrypted prior to Meta’s purchase.
I deleted my WhatsApp account around the time Meta announced they were merging all of their messaging stuff together, e.g. Facebook Messenger, Instagram etc.
Around a year ago WhatsApp had large ads that just said “no one else can read your messages.” I don’t think most people thought that some one could, which makes me wonder why they were paying so much to say it.
Any time they get asked questions like “Are my messages visible only to me?”, they answer with a very canned response like “Your messages are encrypted from end-to-end and can’t be read by anyone while in transit” … or words to that effect. I have never seen them state that no analytics or telemetry is happening on the unencrypted side by the client. Which has always bothered me.
Proposed line of defense: “With all respect, M. Judge, with all the different times we fucked our users, lied to them, tricked them, experimented on them, ignored them, we already sold private discussions on Facebook in the past, our CEO and founder most famous quote is «They trust me, dumbfucks!», the list goes on and on: no one in their sane mind would genuinely believe we were not spying on Whatsapp! They try to play dumb, they could not possibly believe we were being fair and honest THIS time?!”
15 years ago I’d have called this a conspiracy theory given how the evidence seems to be anecdotal, but given literally every single other thing we’ve learned in recent times about how cartoonishly evil and lying the tech bros truly are, it seems entirely likely.
Wait, you are telling me that the company whos entire business is collecting personal information, including people who don’t sign up for their services, to leverage for advertising, is keeping their platforms unsecured they can continually grab more information rather than secure it?
I for one am shocked, absolutely shocked.
Yes, except they’re not leveraging your data for advertising, they’re leveraging it so they can manipulate your political views and keep you from finding solidarity with other working people.
@FlyingCircus @technology These two things are the same thing
Well if I can’t trust Meta with my information, who CAN I trust
The drunk dude that’s always sitting on the ground near the park entrance and sell weird tissue dolls with curly hairs is more trustworthy, I’d say.
Me
Oh okay. My location is 55.752121, 37.617664, my full name is Jeremy, and my password is hunter9. I trust you not to tell this to anybody
Nice to see the ancient lore alive.
Your full name is “Jeremy”?
Oh god damnit chemicalprofet why did you tell this guy i thougjt i could trust you :((
All I see is ‘••••••’
I see ‘******’ though.
Maybe it’s just a different interface.
Jeremy “Iks” Hunter IX
Edit: IX. Iks. I think we got it right now.
The Ninth
Pronounced “iks”
Just like Cher (which is short for Cheremy).
Your secret is safe with us and our 36,893 affiliates.
Can confirm, chemicalprophet is the best password manager I’ve ever used.
Ah! You did your own research!
ta
Shocking.
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.
It is end to end encrypted but they can just pull the decrypted message from the app. This has been assumed for years, since they said they could parse messages for advertising purposes.
Hasn’t it always been that they can decrypt the backups that you personally setup in wa, this way they don’t legally lie to you when the app tells you “this chat is encrypted, even Whatsapp cannot read the messages”.
it’s not even that: they just hold the keys so can simply decrypt your messages with out your clients intervention any time they like
Yep, If they can access messages that are deleted from your device, then they have the keys.
It was obvious.
If I am not adding my own private key to the app, like in Tox, I don’t trust their encryption.
What’s to stop an evil company uploading the keys as soon as you enter them in the App? It certainly wouldn’t stop Meta.
What’s stopping the app from keeping your private key and still not encrypting anything?
I’m not trying to be difficult here, I just don’t see how anything outside of an application whose source you can check yourself can be trusted.
All applications hosted by other people require you to react positively to “just trust me bro”.
Or, if the app has the private key for decryption for the user to be able to see the messages, what’s stopping the app from copying that decrypted text somewhere else?
The thread model isn’t usually key management, it’s more about the insecure treatment of the decrypted message after decryption.
Tox also isn’t that great security wise. It’s hard to beat Signal when it comes to security messengers. And Signal is open source so, if it did anything weird with private keys, everyone would know
And Signal is open source so, if it did anything weird with private keys, everyone would know
Well, no. At least not by default as you are running a compiled version of it. Someone could inject code you don’t know anything about before compilation that for example leaked your keys.
One way to be more confident no one has, would be to have predictable builds that you can recreate and then compare the file fingerprints. But I do not think that is possible, at least on android, as google holds they signature keys to apps.
Signal is also on F-Droid, so it should be verifiable
Signal has reproducible builds and here’s the instruction how to check it on Android https://github.com/signalapp/Signal-Android/blob/main/reproducible-builds/README.md
Well, Whatsapp uses signal. Bad timing
It only uses some of signal’s code. Not necessarily the OOTB key storage and security.
How?
Read more than just the title ffs
I did and nowhere is Signal mentioned in the article.
You state Whatsapp uses Signal. So, again: how?
The article does not describe what encryption it uses, it described how they’re abusing it. Whatsapp using Signal protocol is public knowledge.
What I’m trying to say is that a company using signal for it’s messaging app does not imply your data is safe from that company or governments.
You recommending an app purely because of Signal protocol under an article about how an app abuses signal protocol is pretty fucking ironic (aka. bad timing)
Unless proof is given, assume troll
Read the article? An app using signal does not imply that your data is still encrypted from corporations or government. Your neighbour joe is not very likely to break already established SSL, so using signal feels like someone is trying to sell me a bridge. Sense of false security. In fact, that was probably their goal all along.
WhatsApp is using Signals protocol for communication: https://signal.org/blog/whatsapp-complete/
I don’t fully understand what it entails, but from what I understand is that yes, WhatsApp is using the same encryption and message flow that signal uses, but you’re still using Meta’s app, and they can just read the plaintext message from there.
Or they can make a copy of the encryption keys on creation. Using the code is very different than using the code unedited, or using all the code.
To my knowledge, under Signal, the encription keys are locally generated and stored, and the traffic flows between end points as a closed packet.
This does not seem to be the case here, as the keys are generated and stored outside your equipment and, thus, are viable to be used by a third party to access packets.
But I admit I speak heavily burdened by technical ignorance.
My understanding is they’re sending a request to your device that then decrypts and uploads messages, not storing the keys outside your device.
that’s incorrect. with whatsapp, your keys are stored on meta servers (the same as things like imessage). they can simply decrypt them whenever they like, just like being signed in as you. it’s completely invisible to your client
Man, you just brought back memories. I forgot qtox was even a thing. I think I still have my profile saved in my dev folder somewhere for my account
Assume the same for Telegram and pretty much any chat platform that controls your private keys.
Telegram doesnt even pretend to be end to end encrypted.
Telegram for iOS lets you create “secret chats” but as far as I know other platforms have eliminated that functionality at the request of governments. And I would assume Apple technically controls the keys on device.
iOS lets you create “secret chats”
How? Not natively unless I’m mistaken
Not natively that I know of, but Telegram for iOS has the option when looking at someone’s profile. However, the Windows client does not.
The telegram was clear as a day they announced cooperation with the Russian government and they unblocked it. That was way before the whole France fiasco, I doubt they’re actually giving up the keys to France. I’m from East and many say that Telegram now is essentially a Russian weapon. Surveillance at home, total free reign (sell drugs, spread CP, etc.) in west.
If you’re American, I believe Telegram is actually safer than Whatsapp, as long as you can ignore the dirty side of it (surface deep web?), hence why Europe wants it under control
DUH
No if this is proven it would be a real scandal and would bring a lot of users to better alternatives.
If it’s false that’s good too, since then WA has e2e encryption
would bring a lot of users to better alternatives.
Most users of whatsapp don’t care about e2e. They hardly even know what it is.
“Your messages are public and being read by silicon valley creeps”
That’s easy enough to understand.
True. But some would care about broken promises
They don’t know what e2e encryption is, but they sure as hell know what “employees have access to all your messages” means. Sure, it makes it harder for them to find a good alternative, but it will scare some away from Meta (unknown how many will actually care).
Right. This place sometimes forget that we are tiny community of techies that hate the system. Makes me see this place as a bit of a circlejerk at times.
Yeah the venn diagram overlap of “people who understand and care about e2ee enough to drop a messaging app for not supporting it” and “people who use whatsapp” has to be a sliver
It must really be empty… Two contradictory assumptions lol
Not empty… It’s hard to embark all your family, relatives and friends on your journey to fucking basic privacy principles
No but average people understand the concept of meta reading and accessing your private message. That would be a scandal and righly so
They don’t but they do know what “Any Meta employee, and every US government employees, can read all of your messages” means
Especially if they saw it now
If it’s false
How would we know?
It’s already a known risk, because WA uses centralized key management and servers, and always has regardless what Meta says. If you believe their bullshit, then I feel sad for you.
Also…you don’t think that LAWYERS willing to go up against Meta would have rock solid proof from these whistleblowers FIRST before filing a lawsuit?
C’mon now, buddy.
What do you want from me here?
I’m surprised anyone is surprised. It’s been known since WhatsApp came out that it’s not true e2ee because meta holds your keys.
Well they did this whole stupid “rebranding” of it becoming e2e after Facebook bought them a few years back, but literally every security researchers was like “Nahhhh, pass”.
considering that you can decrypt facebook e2e encryption with a 6 digit security pin… yea Facebook at least has the private keys backed up server side.
I don’t use any Meta products, so not sure how you mean. If you are a user that has been sending e2e messages, then you can surely decrypt said messages if you’re a participant in those messages transactions.
So, with facebook if you lose your device, you can register a new device to the account and recover your messages using a 6 digit security pin or a recovery code.
This means that your messages are stored in decryptable format either via a private key being stored, or as a separate server encrypted form in a backup.
I just had to go through this with my grandfather a few months back.
Also…you don’t think that LAWYERS willing to go up against Meta would have rock solid proof from these whistleblowers FIRST before filing a lawsuit?
This is not how civil court works. It’s not trial by combat. There is no standard for the quality of lawsuits filed. And despite what the ambulance chasers say on TV, Layers get paid even when they loose.
“alleged in a lawsuit…” is the same level of credibility as “they out here saying…”.
It doesn’t matter if it’s criminal or civil. The costs to bring such a case are massive, and you’re leaving yourself open to a behemoth like Meta just dragging out the case for lengthy periods of time which drastically increase those costs.
No law firm files suit against a giant company like this unless they have rock solid proof they will, at the very least, land a settlement plus recuperation of costs. Just not a thing.
Mark zuckerberg eats scandals for breakfast
Yes but Whatsapp has been pretty reliable and trustworthy for many people. No ads etc
People wouldnt move. They know its not secure and they dont care enough.
we can’t lose!
It would not. People don’t care. People don’t care that meta is an evil corp. Encryption is not even close to the top 10 reasons people use that app. It’s just a random word normal users throw around because marketing told them it’s good.
Normal users don’t talk about encryption at all but they somewhat trust WhatsApp
What are the better alternatives? because it seems like the comment section is flooded with people (yourself included) that don’t understand that most (probably all) e2e messaging apps are vulnerable to this attack as long as they trust a centralized server.
The issue isn’t an encryption one, it’s a trust one that requires you to trust the makers of the messaging app and the servers the apps connect to (and the method by which the app is distributed to you).
What is your alternative? Everybody codes their own app??
Also you’re unhinged in these comments
People should understand the limits of E2E encryption.
I’d rather be unhinged than wrong.
Briar. Designed for, for example, journalists in countries that may persecute them for saying the wrong thing. Can technically be run completely on a mesh network, meaning it’s actually truly decentralized.
Signal uses reproducible builds for its Android client, and I think for desktop as well. That means it’s possible to verify that a particular Signal package is built from the open source Signal codebase. I don’t have to trust Signal because I can check or build it myself.
If I don’t have extreme security needs, I don’t even have to check. Signal has a high enough profile that I can be confident other people have checked, likely many other people who are more skilled at auditing cryptographic code than I am.
Trusting the server isn’t necessary because the encryption is applied by the sender’s client and removed by the recipient’s client.
likely many other people who are more skilled at auditing cryptographic code than I am
Maybe but that doesn’t mean you have the same app they do, Google may have different apks for people who could check it and for those who won’t.
Signal
You’re just replacing trust in Meta with trust in Signal Inc without understanding why WhatsApp is vulnerable to this.
Is Signal Inc more trustworthy than Meta? probably
is Signal (app) safe from the attack described? absolutely not.
Theoretically, you can check the code actually running on the Signal servers is the code they publish under a free and open source licence, using the hardware-based TEE attestations the servers will return
Someone more knowledgeable than me may have managed to do so, I haven’t.
Tell me you don’t understand how Signal’s E2E mechanism works without telling me you don’t understand how Signal’s E2E mechanism works.
Tell me you don’t understand what E2E encryption is without telling me you don’t understand that the limits of E2E encryption.
See every other comment in this thread describing in great detail why you are wrong, but that you fundamentally DO NOT UNDERSTAND how any of this works whatsoever.
You fundamentally DO NOT UNDERSTAND how security works, go play with your algorithms and stop spamming my replies.
Um, security is based largely on encryption algorithms.
This is key and I don’t think Signal shies away from this. You MUST trust the code you’re running. We know there are unofficial Signal builds. You must trust them. Why? Because think of it this way. You’re running a build of Signal, you type a messages. In code that text you type then gets run through Signal’s encryption. If you’re running a non-trustworthy build, they have access to the clear text before encryption, obviously. They can encrypt it twice, once with their key and once with yours, send it to a server, decrypt theirs and send yours on to it’s destination. (for example, there’s more ways than this).
The code can be okay but it’s delivery method(aka Google), the OS(aka Google) or the hardware can be compromised.
Just because it’s centralized doesn’t mean that it falls under this risk sector. Theoretically if the app was open sourced and was confirmed to not share your private key remotely on generation (or cross sign the key to allow a master key…), then the most the centralized server could know is your public key, the server wouldn’t have the ability to obtain the private key (which is what is needed to read the e2e encrypted messages)
This process would be repeated for the other party. The cool part of that system is you can still share your public keys via the centralized server, so you wouldn’t need to share the key externally. You just need to be able to confirm that the app itself doesn’t contain code to send your private key to the centralized server. Then checking integrity is as easy as messaging your friend to post what their public key is, and that public key would need to match the public key that the server is supplying as your contact.
The server can’t MiTM attack it because the server has no way of deciphering the message in the first place, so the most it could do is pass the message onto the proper party whom has the private key to be able to decrypt it.
Not that I have any other suggestions aside from signal though, there aren’t many centralized e2e chat services. Most use client to server encryption which would allow decryption server side.
Just because it’s centralized doesn’t mean that it falls under this risk sector.
The attack as described almost certainly involves the server sending a message to your client and then having the messages replicated via a side channel to Whatsapp without breaking E2E encryption (it could be adding them as a desktop client or adding them as a hidden participant in all chats, that isn’t clear in the article)
If you could run Whatsapp without connecting to Meta, you would be safe from this attack, but as you’ve pointed out a secure client is a better solution.
Fully agree that in this case if the claim is true (they have had a few of these claims), it’s likely whatsapp either making itself a companion app that’s hidden, or has some form of escrow in place to allow deciphering the messages. (Considering Messenger allows decrypting e2e chats with a 6 digit security pin, I’m leaning towards an escrow)
I was just mentioning that this isn’t a fault of it being centralized, this is a design choice by the company when implementing e2e encryption, and that a properly functioning system would never give the server the ability to decipher the messages in the first place.
Element / matrix.
With e2e you don’t need to trust the servers. You only need to trust the client that does the encryption.
Should you not also trust your device hardware, it’s os and the market you got the app from?
That’s a given I think. If you can’t trust the OS then you can’t trust the client.
The attack as described almost certainly involves the server sending a message to your client and then having the messages replicated via a side channel to Whatsapp without breaking E2E encryption.
But yes the point is you can’t trust the clients.
If you could run Whatsapp without connecting to Meta, you would be safe from this attack, but as you’ve pointed out a secure client is a better solution.
Shocked, I tell you
Why am I not surprised? Whether there is no end-end encryption, they have a copy of every key, get the decrypted messages from the client, or can ask the client to surrender the key - it does not matter.
The point is that they never intended to leave users a secure environment. That would make the three latter agencies angry, and would bar themselves from rather interesting data on users.
