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:   Thu, 13 Jan 2022 14:45:36 -0800
From:   Alexei Starovoitov <>
To:     "Jason A. Donenfeld" <>
Cc:     Toke Høiland-Jørgensen <>,
        Network Development <>,
        LKML <>,
        Geert Uytterhoeven <>,
        Herbert Xu <>,
        Ard Biesheuvel <>,
        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 Thu, Jan 13, 2022 at 4:27 AM Jason A. Donenfeld <> wrote:
> Hi Alexei,
> On 1/13/22, Alexei Starovoitov <> wrote:
> > Nack.
> > It's part of api. We cannot change it.
> This is an RFC patchset, so there's no chance that it'll actually be
> applied as-is, and hence there's no need for the strong hammer nack.
> The point of "request for comments" is comments. Specifically here,
> I'm searching for information on the ins and outs of *why* it might be
> hard to change. How does userspace use this? Why must this 64-bit
> number be unchanged? Why did you do things this way originally? Etc.
> If you could provide a bit of background, we might be able to shake
> out a solution somewhere in there.

There is no problem with the code and nothing to be fixed.

Powered by blists - more mailing lists