Live data from Hacker News

The Problem with Perceptual Hashes

rentafounder.com

161–170 of 440 posts

Re: The Problem with Perceptual Hashes

#161
post #155
post #110

The problem of hash or NN based matching is, the authority can avoid explaining the mismatch. Suppose the authority want to false-arrest you. They prepare a hash that matches to an innocent image they knew the target has in his Apple product. They hand that hash to the Apple, claiming it's a hash from a child abuse image and demand privacy-invasive searching for the greater good. Then, Apple report you have a file th…

Well, presumably at that point, someone in that position would just reveal their own files with the hash an prove to the public that they weren't illegal. Sure, it would be shitty to be forced to reveal your private information that way, but you would expose a government agency as fabricating evidence and lying about the contents of the picture in question to falsely accuse someone. It seems like that would be a scan…

[deleted]

Re: The Problem with Perceptual Hashes

#162
This article focusses too much on the individual case, and not enough on the fact that Apple will need multiple matches to report someone. Images would normally be distributed in sets I suspect, so it is going to be easy to detect when someone is holding an offending set because of multiple matches. I don't think Apple are going to be concerned with a single hit. Here in the news offenders are reported as holding many thousands of images.

Re: The Problem with Perceptual Hashes

#163

Earlier quoted context omitted.

You don't plan to ever use 4G/5G again?

I have openvpn so the block will remain in effect. I don't plan to use apple services ever again but the hard ware is pretty good.

Does this mean you are attempting to use an IP range block to avoid this "service" while continuing to use Apple hardware? How does such a block deal with say, Apple software conveniently "routing-around" what appears to be an "authoritarian government's firewall?"

Re: The Problem with Perceptual Hashes

#164

Earlier quoted context omitted.

Rookie mistake. Three rules to live by: 1) Always pay your taxes 2) Don’t talk to the police 3) Don’t take photographs with your clothes off

I might amend #2 a bit to read "Be friends with the police" as that has historically been more beneficial to those who are.

The point that being friends with police will be beneficial to you - Means there's a scenario where the inverse is also true. Not being friends with police is used to your detriment.

Police Officers exist in a career field that is riddled with incidents of Tunnel Vision. The sibling comment posts a video about not talking to police from a law professor. I'd heed that advice.

Re: The Problem with Perceptual Hashes

#165
post #59

The method Apple is using looks more like a cryptographic hash. That's entirely different (and more secure) than a perceptual hash. From https://www.apple.com/child-safety/ "Before an image is stored in iCloud Photos, an on-device matching process is performed for that image against the known CSAM hashes. This matching process is powered by a cryptographic technology called private set intersection, which determines…

The crypto here is for the private set intersection, not the hash. So your device has a list of perceptual (non-cryptographic) hashes of its images. Apple has a list of the hashes of known bad images. The protocol lets them learn which of your hashes are in the “bad” set, without you learning any of the other “bad” hashes, and without Apple learning any of the hashes of your other photos.

Well therein lies the problem: perceptual hashes don't produce an exact result. You need to compare something like the hamming distance (as the article mentions) of each hash to decide if it's a match.

Is it possible to perform private set intersection where the comparison is inexact? I.e., if you have two cryptographic hashes, private set intersection is well understood. Can you do the same if the hashes are close, but not exactly equal?

If the answer is yes, that could mean you would be able to derive the perceptual hashes of the CSAM, since you're able to find values close to the original and test how far you can drift from it before there's no longer a match.

Re: The Problem with Perceptual Hashes

#166
What is the ratio of consumers of child pornography to the population of iPhone users? In order of magnitude, is it 1%, 0.1%, 0.001%, 0.0001%? With all the press around the announcement, this is not exactly stealth technology. Wouldn't such consumers switch platforms, rendering the system pointless?

Re: The Problem with Perceptual Hashes

#167
post #156
post #72

The technical challenges aside, I’m very disturbed that my device will be reporting me to the authorities. That’s very different from authorities taking a sneak peek into my stuff. That’s like the theological concept of always being watched. It starts with child pornography but the technology is indifferent towards it, it can be anything. It’s always about the children because we all want to save the children. Soon t…

With you up to here, but this is jumping the shark > I bet you, after the next election in the US your device will be reporting you for spreading far right or deep state lies, depending on who wins. The US is becoming less stable, sure [1], but there is still a very strong culture of free speech, particularly political speech. I put the odds that your device will be reporting on that within 4 years as approximately 0…

>but there is still a very strong culture of free speech

In my opinion, that culture has been rapidly dying, chipped away by a very sizable and growing chunk that doesn't value it at all, seeing it only as a legal technicality to be sidestepped.

Re: The Problem with Perceptual Hashes

#168
post #22

> an Apple employee will then look at your (flagged) pictures. This means that there will be people paid to look at child pornography and probably a lot of private nude pictures as well.

Apple, with all those Apple == Privacy billboards plastered everywhere, is going to have a full-time staff of people with the job of looking through it's customers' private photos.

Sue them for false marketing.

Re: The Problem with Perceptual Hashes

#169
post #160
post #156

Earlier quoted context omitted.

With you up to here, but this is jumping the shark > I bet you, after the next election in the US your device will be reporting you for spreading far right or deep state lies, depending on who wins. The US is becoming less stable, sure [1], but there is still a very strong culture of free speech, particularly political speech. I put the odds that your device will be reporting on that within 4 years as approximately 0…

Apple has a shitty record wrt free speech. Apple hates free speech. Apple likes “curation”. They canned Parler in a heartbeat; they also police the App Store for anything naughty.

Canning Parler is Apple choosing not to advertise and send you an app they don't like, i.e. it's Apple exercising it's own right to free speech. Agree or disagree with it, it's categorically different from Apple spying on what the files you have are saying (not even to or via Apple) and reporting it to the government.

Re: The Problem with Perceptual Hashes

#170
post #72

The technical challenges aside, I’m very disturbed that my device will be reporting me to the authorities. That’s very different from authorities taking a sneak peek into my stuff. That’s like the theological concept of always being watched. It starts with child pornography but the technology is indifferent towards it, it can be anything. It’s always about the children because we all want to save the children. Soon t…

I would really like people to start answering this: what exactly do you think has changed? e.g, >That’s very different from authorities taking a sneak peek into my stuff. To be very blunt: - The opt out of this is to not use iCloud Photos. - If you _currently_ use iCloud Photos, your photos are _already_ hash compared. - Thus the existing opt out is to... not use iCloud Photos. The exact same outcome can happen regar…

I think one of the major factors that changes how people perceive this is that it's happen on their own device. If you upload a thing to a server and the server does something... I mean sure. You gave a thing to somebody else, and they did something with it. That's a very understandable and largely accepted situation.

This is different. This is your own device doing that thing, out of your control. Alright sure, it's doing the same thing as the other server did and under the same circumstances* so maybe functionally nothing has changed. But the philosophical difference is quite huge between somebody else's server watching over what you upload and your own device doing it.

I'm struggling to come up with a good analogy. The closest I can really think of is the difference between a reasonably trusted work friend and your own family member reporting you to the authorities for suspicious behavior in your workplace and home respectively. The end result is the same, but I suspect few people would feel the same about those situations.

* There is no inherent limitation for your own device to only be able to check photos you upload to iCloud. There is however such a limitation for the iCloud servers. A very reasonably and potentially functional difference is the ability for this surveillance to be easily expanded beyond iCloud uploads in the future.

Post reply on HN