On Wed, Jan 12, 2022 at 7:50 PM David Sterba <dsterba@xxxxxxx> wrote: > > On Wed, Jan 12, 2022 at 02:12:01PM +0100, Jason A. Donenfeld wrote: > > Hi, > > > > There are currently two remaining users of SHA-1 left in the kernel: bpf > > tag generation, and ipv6 address calculation. In an effort to reduce > > code size and rid ourselves of insecure primitives, this RFC patchset > > moves to using the more secure BLAKE2s function. > > What's the rationale to use 2s and not 2b? Everywhere I can find the 2s > version is said to be for 8bit up to 32bit machines and it's worse than > 2b in benchmarks (reading https://bench.cr.yp.to/results-hash.html). > > I'd understand you go with 2s because you also chose it for wireguard > but I'd like know why 2s again even if it's not made for 64bit > architectures that are preferred nowadays. Fast for small inputs on all architectures, small code size. And it performs well on Intel - there are avx512 and ssse3 implementations. Even blake3 went with the 32-bit choice and abandoned 2b's thing. Plus, this makes it even more similar to the well trusted chacha permutation. As far as a general purpose high security library (keyed) hash function for internal kernel usages, it seems pretty ideal. Your choice for btrfs though is fine; don't let this patchset change your thinking on that. Anyway, I hope that's interesting to you, but I'm not so much interested in bikeshedding about blake variants as I am in learning from the net people on the feasibility of getting rid of sha1 in those two places. So I'd appreciate it if we can keep the discussion focused on that and not let this veer off into a tangential thread on blakes.
