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  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:   Mon, 26 Dec 2016 17:51:14 +0000
From:   Ard Biesheuvel <>
To:     Herbert Xu <>
Cc:     Andy Lutomirski <>,
        Andy Lutomirski <>,
        Daniel Borkmann <>,
        Netdev <>,
        LKML <>,
        Linux Crypto Mailing List <>,
        "Jason A. Donenfeld" <>,
        Hannes Frederic Sowa <>,
        Alexei Starovoitov <>,
        Eric Dumazet <>,
        Eric Biggers <>,
        Tom Herbert <>,
        "David S. Miller" <>
Subject: Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be
 used without shash

On 26 December 2016 at 07:57, Herbert Xu <> wrote:
> On Sat, Dec 24, 2016 at 09:57:53AM -0800, Andy Lutomirski wrote:
>> I actually do use incremental hashing later on.   BPF currently
>> vmallocs() a big temporary buffer just so it can fill it and hash it.
>> I change it to hash as it goes.
> How much data is this supposed to hash on average? If it's a large
> amount then perhaps using the existing crypto API would be a better
> option than adding this.

This is a good point actually: you didn't explain *why* BPF shouldn't
depend on the crypto API.

Powered by blists - more mailing lists