Re:Tainting the CSAM client-side scanning database
by viridian on Friday October 13, 2023 @02:13PM
(#37873670)
I agree that it's not hash collision, but the fingerprinting strategy makes precise language on this topic a bit difficult/tedious.
The CSAM detection isn't proper hash collision either, in so far as I understand it. There's some fuzzy matching formula that generates the fingerprint, it's not simply a byte for byte hash taken of the image, and therein lies the comparison.
The fraud in question is reliant on content ID attempting to fuzzy match audio content, in this specific instance.
The CSAM detection isn't proper hash collision either, in so far as I understand it. There's some fuzzy matching formula that generates the fingerprint, it's not simply a byte for byte hash taken of the image, and therein lies the comparison.
The fraud in question is reliant on content ID attempting to fuzzy match audio content, in this specific instance.