Re:SipHash and HalfSipHash Added to Linux Kernel
by wolf550e on Tuesday January 10, 2017 @06:52AM
(#13364195)
The danger in your scheme is that an attacker who finds a way to see lots of keyed hash values in one hash table can flood a different hash table. You should keep a 16 byte key per hash table.
Re:SipHash and HalfSipHash Added to Linux Kernel
by grey-area on Tuesday January 10, 2017 @07:31AM
(#13364343)
Thanks, I'll only have one set of hashes. My question was really is it ok to use one key per table of hashes, or does it have to be one key per hash. I think you're saying one per table is fine, but wanted to be sure I wasn't doing it wrong. I'll have another look for examples.
Is it ok to use the same random key with siphash for lots of different hashes as long as the key is secret and mutates once per launch (i.e. generating once on app startup and use it for all hashes)?