| Message ID | 20220421204320.258010-1-ebiggers@kernel.org (mailing list archive) |
|---|---|
| State | Not Applicable |
| Delegated to: | Herbert Xu |
| Headers | show |
| Series | siphash: update the HalfSipHash documentation | expand |
Hi Eric, On Thu, Apr 21, 2022 at 10:44 PM Eric Biggers <ebiggers@kernel.org> wrote: > -Danger! > +**Danger!** HalfSipHash should only be used in a very limited set of use cases > +where nothing better is possible, namely: > > -Do not ever use HalfSipHash except for as a hashtable key function, and only > -then when you can be absolutely certain that the outputs will never be > -transmitted out of the kernel. This is only remotely useful over `jhash` as a > -means of mitigating hashtable flooding denial of service attacks. > +- Hashtable key functions, where the outputs will never be transmitted out of > + the kernel. This is only remotely useful over `jhash` as a means of mitigating > + hashtable flooding denial of service attacks. I think we should actually drop this chunk of the patch. You wrote in your commit message, "HalfSipHash-1-3 is not entirely limited to hashtable functions, with it now being used in the interrupt entropy accumulator." But in fact, random.c uses HalfSipHash-1, with no three round finalization (since we use BLAKE2s for that). So it's not _quite_ the same thing. If it were, we could have gotten away by just calling the actual hsiphash function, but instead it's just applying the round function as a permutation. If you feel strongly that somebody might accidentally copy and paste that after grepping for halfsiphash and trying to figure out how to use it, I suppose we could keep this. But it strikes me as very much not the same thing as the hsiphash_* family of functions. Jason
On Fri, Apr 22, 2022 at 01:08:01AM +0200, Jason A. Donenfeld wrote: > Hi Eric, > > On Thu, Apr 21, 2022 at 10:44 PM Eric Biggers <ebiggers@kernel.org> wrote: > > -Danger! > > +**Danger!** HalfSipHash should only be used in a very limited set of use cases > > +where nothing better is possible, namely: > > > > -Do not ever use HalfSipHash except for as a hashtable key function, and only > > -then when you can be absolutely certain that the outputs will never be > > -transmitted out of the kernel. This is only remotely useful over `jhash` as a > > -means of mitigating hashtable flooding denial of service attacks. > > +- Hashtable key functions, where the outputs will never be transmitted out of > > + the kernel. This is only remotely useful over `jhash` as a means of mitigating > > + hashtable flooding denial of service attacks. > > I think we should actually drop this chunk of the patch. You wrote in > your commit message, "HalfSipHash-1-3 is not entirely limited to > hashtable functions, with it now being used in the interrupt entropy > accumulator." But in fact, random.c uses HalfSipHash-1, with no three > round finalization (since we use BLAKE2s for that). So it's not > _quite_ the same thing. If it were, we could have gotten away by just > calling the actual hsiphash function, but instead it's just applying > the round function as a permutation. > > If you feel strongly that somebody might accidentally copy and paste > that after grepping for halfsiphash and trying to figure out how to > use it, I suppose we could keep this. But it strikes me as very much > not the same thing as the hsiphash_* family of functions. Well, this documentation starts out by introducing HalfSipHash, and then moves on to the the hsiphash functions. This part is still talking about HalfSipHash, so in that context the mention of its use in random.c is relevant. But I could certainly reword it to make it all about the hsiphash functions, with HalfSipHash being mentioned more as an implementation detail. - Eric
Hi Eric, On Fri, Apr 22, 2022 at 1:40 AM Eric Biggers <ebiggers@kernel.org> wrote: > Well, this documentation starts out by introducing HalfSipHash, and then moves > on to the the hsiphash functions. This part is still talking about HalfSipHash, > so in that context the mention of its use in random.c is relevant. But I could > certainly reword it to make it all about the hsiphash functions, with > HalfSipHash being mentioned more as an implementation detail. Alright, so let's just drop that hunk for v2 then. Jason
diff --git a/Documentation/security/siphash.rst b/Documentation/security/siphash.rst index bd9363025fcbc..9b079b2ac2a1a 100644 --- a/Documentation/security/siphash.rst +++ b/Documentation/security/siphash.rst @@ -121,15 +121,23 @@ even scarier, uses an easily brute-forcable 64-bit key (with a 32-bit output) instead of SipHash's 128-bit key. However, this may appeal to some high-performance `jhash` users. -Danger! +**Danger!** HalfSipHash should only be used in a very limited set of use cases +where nothing better is possible, namely: -Do not ever use HalfSipHash except for as a hashtable key function, and only -then when you can be absolutely certain that the outputs will never be -transmitted out of the kernel. This is only remotely useful over `jhash` as a -means of mitigating hashtable flooding denial of service attacks. +- Hashtable key functions, where the outputs will never be transmitted out of + the kernel. This is only remotely useful over `jhash` as a means of mitigating + hashtable flooding denial of service attacks. -Generating a HalfSipHash key -============================ +- The interrupt entropy accumulator in ``drivers/char/random.c``. This is a very + special case; do *not* use this as example code for anything else. + +Note, 64-bit kernels actually implement SipHash-1-3 instead of HalfSipHash-1-3; +the "hsiphash" functions redirect to either algorithm. This is done for +performance reasons; it does *not* mean that the hsiphash functions are +cryptographically secure on 64-bit platforms. + +Generating a hsiphash key +========================= Keys should always be generated from a cryptographically secure source of random numbers, either using get_random_bytes or get_random_once: @@ -139,8 +147,8 @@ get_random_bytes(&key, sizeof(key)); If you're not deriving your key from here, you're doing it wrong. -Using the HalfSipHash functions -=============================== +Using the hsiphash functions +============================ There are two variants of the function, one that takes a list of integers, and one that takes a buffer::