Retr0spectrum
Joined 12 years ago
Joined 12 years ago
The images shown do appear to be adversarially generated inputs against some NN-based image hash or classifier, but there is no evidence to suggest that this is at all related to Apple's NeuralHash, or that the colliding hashes are from a real CSAM database (the target hashes are not public).
OP claimed they would "release 5 pieces of proof in the next 5 days" [1], and guess what, 11 days later they still haven't.
Look at OP's post and comment history, it's quite clear that they are a troll.
In the mean time, it has been actually proven that hash collisions against NeuralHash are trivially possible, see [2]
Why 2 minutes? I assume this is used as a stand-in for "very short time", because there's no way it actually takes two minutes to install unless your internet is particularly slow, and I don't imagine there's much to configure.
It seems a bit out of place, especially when the extension itself centers around the problem of 5 seconds feeling like an eternity.
Edit: I just installed it as a test, and it was ~instant.
Out of the 45 search results, the most relevant one (the UDP RFC itself) was all the way at the bottom, listed as "RFC0768" and tagged as "legacy". (I'm not sure what legacy actually means here?)
Anyway, I clicked the link, which took me to a 404 error page - https://www.rfc-editor.org/rfc/rfc0768.html (The correct URL is apparently without the leading 0)
This site does seem genuinely useful, but I think the UX could really use some polishing here, especially since I literally followed through with one of the example queries in the middle of the homepage.
However, the fun part about this particular attack is that it does not require quite the same level of precision. The voltage is dropped incrementally until the CPU starts to make faulty calculations. It just so happens that AES is one of the most complex operations, and thus, the first to start faulting.