This repository was archived by the owner on May 13, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on May 13, 2022. It is now read-only.
SpookyHashV2 hashes do not match official implementation #30
Description
The 32 bit spookyhashv2 of the string "hello world" should be UInt32 "2617184861" according to the official implementation But with this library it is not.
I have tested all possible ways of feeding this string including different encodings and none of them match.
Testing the same thing with other libraries and this website match properly
https://asecuritysite.com/encryption/Spooky
Activity
brandondahler commentedon Nov 2, 2017
Going through the history, it appears that the initial implementation was never correct and therefore all versions of Data.HashFunction.SpookyHash have been producing incorrect values, checked against incorrect test vectors. Because of this, I am going to unlist all existing versions of this package from NuGet.
I will fix and re-release a fixed implementation as soon as I am able to.
brandondahler commentedon Nov 25, 2017
Looking at the implementation, it appears that the root cause of the error is because it was incorrectly assumed that the Short(...) function call for byte lengths of 192 and less were just optimizations of the core hash implementation.
This assumption is incorrect -- SpookyHash has a slightly different hash generation implementation for input values of < 192 bytes in length.
The net effect is that we have been producing incorrect results for all values < 192 bytes in length.
brandondahler commentedon Mar 27, 2018
I have verified that this has been resolved in v2.0.