News for hackers. Stuff that matters.
Re:Hash collision in Apple NeuralHash model by floatingatoll on Wednesday August 18, 2021 @03:09PM (#28225793)
Why would they bother? That's a terrible way to approach it.

Just pass legislation requiring in-country datacenters that can be decrypted by thoughtcrime enforcers, like Russia and China are doing. Trying to get this done via a CSAM list that's absurdly closely audited would be a huge waste of time and not provide any significant benefit, and if such a request were ever made public, would likely result in severe political and economic sanctions.

That's what everyone's missing in this argument. There's no need to be all underhanded and secretive when you can just pass laws and conduct military-backed demands upon companies using those laws. Trying to exploit the CSAM process would be a horrifically bad idea, and would result in public exposure and humiliation, rather than the much more useful outcome that simply passing a law would provide.

Re:Hash collision in Apple NeuralHash model by neolog on Wednesday August 18, 2021 @05:12PM (#28227238)
Without the technology deployed, Apple can (and did) say they don't have the ability to break into users' phones.

If Apple deploys on-phone scanning, governments can just tell Apple to support a new list. It won't be the NCMEC CSAM list. It will be a "public safety and security" list. I wouldn't rule out underhandedness either. [1]

[1] https://www.nytimes.com/2020/07/01/technology/china-uighurs-...

Re:Hash collision in Apple NeuralHash model by floatingatoll on Wednesday August 18, 2021 @05:31PM (#28227439)
Apple already has technology deployed to perform binary file scans of every file on macOS and iOS, and the ability to at any time release signatures for those scans, that are very difficult for normal users to prevent updates for. They've had that for years, maybe even a decade by now, and so far to date we have seen no abuse of that list.

How is Apple's new CSAM list somehow increasing the chances of Apple going rogue, given that we've all been living with that risk for the past X years?

Re:Hash collision in Apple NeuralHash model by neolog on Wednesday August 18, 2021 @05:45PM (#28227582)
What technology are you referring to as already deployed?
Re:Hash collision in Apple NeuralHash model by floatingatoll on Wednesday August 18, 2021 @06:02PM (#28227722)
For macOS, I'm talking about XProtect and MRT. I don't know the exact subsystem names on iOS, apologies.

https://support.apple.com/guide/security/protecting-against-...

Each system is closed source, provides a mechanism for checking content signatures against files on disk, and is thought to report telemetry to Apple when signatures are found.

How is CSAM scanning new and different from those existing closed-source systems?

Re:Hash collision in Apple NeuralHash model by neolog on Wednesday August 18, 2021 @06:39PM (#28228043)
I'd say the primary differences are that the CSAM scan is a perceptual hash rather than a regular file hash, and that the technical infrastructure of the CSAM system is designed from the ground up to be used against (rather than for) the user and report them individually to authorities for violation.
Re:Hash collision in Apple NeuralHash model by floatingatoll on Wednesday August 18, 2021 @06:50PM (#28228135)
Do you have an alternate design in mind that is both "used for the user", and is also effective at reporting CSAM content being uploaded from the device, without allowing CSAM abusers to opt-out of that reporting? I haven't been able to come up with anything myself, but maybe you've had better luck.
Re:Hash collision in Apple NeuralHash model by neolog on Wednesday August 18, 2021 @08:27PM (#28228948)
I can only point to other people who know more than me.

https://stratechery.com/2021/apples-mistake/ is a smart tech commentator

https://www.nytimes.com/2021/08/11/opinion/apple-iphones-pri... are two security/encryption experts