4 ms·
The thing that strikes me as most suspicious is their insistence on keeping the client-side scanning feature while wrapping it in all sorts of supposed restrict
by CommieBobDole 5y ago
The thing that strikes me as most suspicious is their insistence on keeping the client-side scanning feature while wrapping it in all sorts of supposed restrictions so it's essentially server-side scanning, just implemented on the client device for some reason.
If the problem is "We need to scan stuff on iCloud for CSAM" then "Let's build a client-side scanning agent and distribute it to hundreds of millions of devices and figure out a way to protect the hashes from the end user and then figure out a way to lock it down so it can't be used to scan other things even if we wanted to or somebody ordered us to" is a singularly (and suspiciously) inelegant solution to the problem.
Just scan the files on your own servers, like everybody else does. Anything else is rightly going to make people suspicious that you've got some ulterior motive.
- zepto 5y agoI assume their goal is to turn on E2E for what gets stored on their servers. Right now, they have to hand over anyone’s photo library if they are ordered to do so. If they turn on E2E that will no longer be possible, and this will be strictly better and harder to abuse. That doesn’t mean this mechanism isn’t offensive. It just is better from a privacy point of view for them to do this and enable E2E.
- willis936 5y agoNotice how they haven't done that though. It would be trivial to do. Just change all of the private keys to ones supplied by the clients. But they haven't done that. Why would you expect them to do that when they are taking steps away from individual privacy? Leaving a hypothetical option on the table that costs them nothing to do means they actively do not want to do it. So why would they do it?
- zepto 5y agoThey haven’t shipped this yet.
- benhurmarcel 5y agoIt’s quite simple, they would like to store photos without being able to see them, only knowing they’re not CP. If they scan on server, they need to be able to see all photos, and eventually give them to any requesting authority. So the reasonable approach is to make clients that only upload photos that are not CP. The problem is that the implementation of that feels creepier than they anticipated.