lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 14 Jan 2022 17:34:44 +0100
From:   "Jason A. Donenfeld" <>
To:     Alexei Starovoitov <>
Cc:     Ard Biesheuvel <>,
        Toke Høiland-Jørgensen <>,
        Network Development <>,
        LKML <>,
        Geert Uytterhoeven <>,
        Herbert Xu <>,
        Jean-Philippe Aumasson <>,
        Linux Crypto Mailing List <>,
        bpf <>
Subject: Re: [PATCH RFC v1 1/3] bpf: move from sha1 to blake2s in tag calculation

On Fri, Jan 14, 2022 at 5:19 PM Alexei Starovoitov
<> wrote:
> On Fri, Jan 14, 2022 at 7:08 AM Ard Biesheuvel <> 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.

It can be removed from vmlinux, and be folded into the crypto API's
generic implementation where it belongs, which then can be built as a
module or not built at all, depending on configuration. Please see the
3/3 patch in this series to see what that looks like:

Meanwhile, you have not replied to any of the substantive issues I
brought up. I'd appreciate you doing so.

Thank you,

Powered by blists - more mailing lists