[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQKCSJi=U4gNv48vsS8Guu7_JP946yMuNqVAJ-D=rAme7w@mail.gmail.com>
Date: Fri, 14 Jan 2022 08:19:12 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: "Jason A. Donenfeld" <Jason@...c4.com>,
Toke Høiland-Jørgensen <toke@...hat.com>,
Network Development <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH RFC v1 1/3] bpf: move from sha1 to blake2s in tag calculation
On Fri, Jan 14, 2022 at 7:08 AM Ard Biesheuvel <ardb@...nel.org> wrote:
>
> Yeah, so the issue is that, at *some* point, SHA-1 is going to have to
> go.
sha1 cannot be removed from the kernel.
See AF_ALG and iproute2 source for reference.
Powered by blists - more mailing lists