SipHash is not designed to be a general-purpose (non-keyed) cryptographic hash, no? But Quark and Spongent look interesting.https://twitter.com/jedisct1/status/993402958263054336 …
You didn’t describe your use case. If offline attacks are irrelevant, or if you’re not expecting 2^64 unique messages with the same key, it’s good enough.
-
-
Interesting. You’re saying that it’s secure (at least against preimages) for publicly known keys if there aren’t many messages with the same key? I’m not an expert, so do you have a source or explanation for this? Off the top of my head it seems reasonable but not obvious.
-
Once again, you didn’t describe your use case. It’s not collision resistant, but it is totally fine if you want to authenticate online messages and stay below the birthday bound.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.