2 ms·
It's not. It's not resistant against hash-flooding attacks, and it's the slowest hash function which is used in the wild. It has some good hash function qualit
by rurban 10y ago
It's not. It's not resistant against hash-flooding attacks, and it's the slowest hash function which is used in the wild.
It has some good hash function qualities, but none of its qualities would qualify it as a good hash table function.
the authors only compare the speed against secure hash functions like MD5 and SHA*, but then are talking about hash tables and compare it against FNV, Murmur and City. (City was replaced by Farm btw. some years ago already)
Below some guys quote my smhasher README, where I tried to get some common sense out.
There are secure hash functions and there are secure hash tables. The topic we are talking here, starting with Robin Hood. But those two topics are mostly orthogonal. A 32-64bit hash function can never be called secure, it's trivial to brute force it. A secure hash function is not usable in a hash table with 32bit, for which 7-15bits are needed for attacks.
Get over it and use proper hash tables, and esp. not linked lists. We are not in the eighties anymore.