News for hackers. Stuff that matters.
Re:Google's TOS doesn't eliminate a user's Fourth Amendment ... by ndriscoll on Wednesday October 30, 2024 @04:16PM (#41999726)
If the hash algorithm were CRC8, then obviously it should not be probable cause for anything. If it were SHA-3, then it's basically proof beyond reasonable doubt of what the file is. It seems reasonable to question how collisions behave.
Re:Google's TOS doesn't eliminate a user's Fourth Amendment ... by cool_dude85 on Wednesday October 30, 2024 @05:01PM (#42000260)
I don't agree that it would be proof beyond reasonable doubt, especially because neither google nor law enforcement can produce the original image that got tagged.
Re:Google's TOS doesn't eliminate a user's Fourth Amendment ... by Dylan16807 on Wednesday October 30, 2024 @07:50PM (#42001901)
By original do you mean the one in the database or the one on the device?

If the device spit out the same SHA3, then either it had the exact same image, or the SHA3 was planted somehow. The idea that it's actually a different file is not a reasonable doubt. It's too unlikely.

Re:Google's TOS doesn't eliminate a user's Fourth Amendment ... by cool_dude85 on Wednesday October 30, 2024 @08:20PM (#42002129)
By the original, I mean the image that was used to produce the initial hash, which Google (rightly) claimed to be CSAM. Without some proof that an illicit image that has the same hash exists, I wouldn't accept a claim based on hash alone.
Re:Google's TOS doesn't eliminate a user's Fourth Amendment ... by Dylan16807 on Wednesday October 30, 2024 @08:26PM (#42002164)
Oh definitely you need someone to examine the image that was put in the database to show it's CSAM, if the legal argument depends on that. But that's an entirely different question from whether the image on the device is that image.