- cross-posted to:
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
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.
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
Most users of whatsapp don’t care about e2e. They hardly even know what it is.
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 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).
True. But some would care about broken promises
“Your messages are public and being read by silicon valley creeps”
That easy enough to understand.
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.
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”.
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.
What do you want from me here?
we can’t lose!
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).
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.
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.
There is a risk Google could tamper with the app for specific users if they’re installing it from Google Play. I think it’s likely security researchers would discover that if it was widespread, but there’s a chance Google could do it undetected if they targeted it selectively enough.
People who are concerned about this can download the APK directly from Signal and check its signature before installation.
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.
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.
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.
No encryption is largely based on encryption algorithms, security is much broader than that.
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.
deleted by creator
People wouldnt move. They know its not secure and they dont care enough.
How would we know?
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
That’s just another comment