- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Zoom Changes TOS to Say It Won’t Train AI on Your Calls ‘Without Your Consent’ After Backlash::Zoom added a line to its terms of use on Monday, after concerns that the company was using calls to train artificial intelligence algorithms went viral.
So if they actually implemented E2E encryption like they said (last time they were called out on lying about it), how exactly would they even collect this information?
You’d need to MITM the calls for it to even be possible, which raises other issues…
Technically they can collect whatever they need, before encrypting to send from E to the other E, and send, with or without encryption, to their servers. The "E"s are the devices on each end, not necessarily the users mouths and ears.
You can send your typed credit card to that site using SSL encryption, but the number can be captured by a keylogger or a screen capture before being encrypted.
So it’s basically “some stuff is E2EE, other stuff is not” which, absent knowing which is which, boils down to no E2EE at all.
Basically this. I don’t assume that just because it’s E2EE (or says it’s E2EE) it’s privacy safe.
Unless maybe if it’s my own system on both sides, running Linux, connected through some FOSS VPN I’ve set up myself, chatting through nc tunneled through ssh with a 100% silent wired keyboard, no monitor, no network, and everything powered off. Inside an underground lead bunker.
That doesn’t mean I don’t use Teams, Whatsapp, Gmail, etc. I just don’t assume it’s private.
True, but in that case you don’t actually have real E2E encryption anymore, as it would need to be sending copies the data to a tertiary destination for processing by AI. The application itself would be the malware (which, TBF is kinda accurate for Zoom anyhow)
E2E just means it’s encrypted from end to end, iow, it’s not decrypted in the middle of the way.
If I was using an E2E communication application, I, for one wouldn’t automatically assume that meant it was not eavesdropping.
Yeah, Zoom could encrypt the data twice with different keys, send one packet to their data collection servers and the other to the other people on the call. It’s still technically E2E encrypted, there’s just two sets of “ends” (origin to data collection and origin to meeting).
Surprise, it’s not end to end encrypted!
Well, not really a surprise. Hell,I wouldn’t be surprised to have it come out and Zoom say “well we didn’t say which end the encryption terminates on”
Lol is it really E2E if you purposely put an MITM in there wtf? What I guess they hand out the private keys?