Re:The Problem with Perceptual Hashes
by Klonoar on Friday August 06, 2021 @09:12PM
(#28094742)
Responding in a separate comment since I either missed the second half, or it was edited in.
>That's neither here, nor there. It's another thing to peak selectively with a warrant of sorts, than to (a) peak automatically in everybody, (b) with a false-positive-prone technique, especially since the mere accusation on a false match can be disastrous for a person, even if they eventually are proven innocent...
I do not believe that iCloud CSAM server side matching ever required a warrant, and I'm not sure where you've gotten this idea. It quite literally is (a) peak automatically in everybody.
Regarding (b), with this way - thanks to them publishing details on it - there's more transparency than if it was done server side.
>especially since the mere accusation on a false match can be disastrous for a person
As noted elsewhere in this very thread, this can happen whether client or server side. It's not unique in any way, shape or form to what Apple is doing here.
Re:The Problem with Perceptual Hashes
by etchalon on Saturday August 07, 2021 @12:57AM
(#28095824)
I'm incredibly amused by the number of supposedly deeply technical and informed people on this site who seem to be unaware of CSAM scanning and its existing use on cloud services.
>That's neither here, nor there. It's another thing to peak selectively with a warrant of sorts, than to (a) peak automatically in everybody, (b) with a false-positive-prone technique, especially since the mere accusation on a false match can be disastrous for a person, even if they eventually are proven innocent...
I do not believe that iCloud CSAM server side matching ever required a warrant, and I'm not sure where you've gotten this idea. It quite literally is (a) peak automatically in everybody.
Regarding (b), with this way - thanks to them publishing details on it - there's more transparency than if it was done server side.
>especially since the mere accusation on a false match can be disastrous for a person
As noted elsewhere in this very thread, this can happen whether client or server side. It's not unique in any way, shape or form to what Apple is doing here.