News for hackers. Stuff that matters.
Re:SeaHash: Explained by kibwen on Friday December 09, 2016 @05:02PM (#13142241)
I believe that you and tptacek may be using differing definitions of "cryptographic", because he tends to knows what he's talking about when it comes to cryptography (e.g. https://gist.github.com/tqbf/be58d2d39690c3b366ad).
Re:SeaHash: Explained by ticki_ on Friday December 09, 2016 @05:46PM (#13142537)
Oh, well.

What I think of as "cryptographic hash function" is a function resistent to pre-image attack, second pre-image attack, and collision generation.

Neither of those are satisfied by SipHash, and can thus not classify as a cryptographic hash function by the normal definition.

Re:SeaHash: Explained by tptacek on Friday December 09, 2016 @06:10PM (#13142679)
It's a cryptographic hash function, but not one suitable for all of the same applications as SHA2. It has security characteristics that other hash-table hashes (for instance) lack.
Re:SeaHash: Explained by ticki_ on Friday December 09, 2016 @06:32PM (#13142830)
If you know the key, it is as weak as it gets (as the paper notes too, you can construct collisions easily if the key is known), so I disagree.
Re:SeaHash: Explained by tptacek on Friday December 09, 2016 @08:04PM (#13143327)
Honestly, I really don't care about this debate, except to the extent that it's about whether SipHash "isn't cryptographic and therefore you might as well use CityHash or SeaHash", which just isn't true.
Re:SeaHash: Explained by ticki_ on Saturday December 10, 2016 @05:50AM (#13145085)
I agree. SipHash is certainly strong if you don't know the key.