Re: [PATCH RFC v2 1/3] bpf: move from sha1 to blake2s in tag calculation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH RFC v2 1/3] bpf: move from sha1 to blake2s in tag calculation
From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
Date: Fri, 14 Jan 2022 08:20:21 -0800
Cc: LKML <linux-kernel@xxxxxxxxxxxxxxx>, Network Development <netdev@xxxxxxxxxxxxxxx>, bpf <bpf@xxxxxxxxxxxxxxx>, Linux Crypto Mailing List <linux-crypto@xxxxxxxxxxxxxxx>, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxxxxxx>, Ard Biesheuvel <ardb@xxxxxxxxxx>, Jean-Philippe Aumasson <jeanphilippe.aumasson@xxxxxxxxx>
In-reply-to: <20220114142015.87974-2-Jason@zx2c4.com>
References: <20220114142015.87974-1-Jason@zx2c4.com> <20220114142015.87974-2-Jason@zx2c4.com>

On Fri, Jan 14, 2022 at 6:20 AM Jason A. Donenfeld <Jason@xxxxxxxxx> wrote:
>
> BLAKE2s is faster and more secure. SHA-1 has been broken for a long time
> now. This also removes quite a bit of code, and lets us potentially
> remove sha1 from lib, which would further reduce vmlinux size.

Same NACK as before.
Stop this spam. Pls.

Follow-Ups:
- Re: [PATCH RFC v2 1/3] bpf: move from sha1 to blake2s in tag calculation
  - From: Jason A. Donenfeld

References:
- [PATCH RFC v2 0/3] remove remaining users of SHA-1
  - From: Jason A. Donenfeld
- [PATCH RFC v2 1/3] bpf: move from sha1 to blake2s in tag calculation
  - From: Jason A. Donenfeld

Prev by Date: Re: [PATCH RFC v1 1/3] bpf: move from sha1 to blake2s in tag calculation
Next by Date: Re: [RFC 15/16] sched/fair: Account kthread runtime debt for CFS bandwidth
Previous by thread: [PATCH RFC v2 1/3] bpf: move from sha1 to blake2s in tag calculation
Next by thread: Re: [PATCH RFC v2 1/3] bpf: move from sha1 to blake2s in tag calculation
Index(es):
- Date
- Thread

[Index of Archives] [Kernel] [Gnu Classpath] [Gnu Crypto] [DM Crypt] [Netfilter] [Bugtraq]