[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251011002601.GB20823@quark>
Date: Fri, 10 Oct 2025 17:26:01 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: David Howells <dhowells@...hat.com>
Cc: "Jason A . Donenfeld" <Jason@...c4.com>,
Ard Biesheuvel <ardb@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Stephan Mueller <smueller@...onox.de>, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/8] crypto, lib/crypto: Add SHAKE128/256 support and
move SHA3 to lib/crypto
Hi David,
On Thu, Oct 02, 2025 at 09:27:05AM -0700, Eric Biggers wrote:
> On Thu, Oct 02, 2025 at 02:14:44PM +0100, David Howells wrote:
> > Eric Biggers <ebiggers@...nel.org> wrote:
> >
> > > Have you had a chance to read this reply?
> >
> > I have.
> >
> > You held up your implementation of sha256 and sha224 as an example of how it
> > perhaps should be implemented:
> >
> > It would be worth considering separating the APIs for the different
> > algorithms that are part of SHA-3, similar to what I did with SHA-224
> > and SHA-256.
> >
> > so I have followed that. That defines a type for each, so I'll leave it at
> > that.
>
> In v3, you were pretty clear that you don't like the six-types solution:
Let me know if you have a new version of this patchset planned.
Otherwise I'll work on cleaning it up and finishing the remaining parts,
like incorporating the arch-optimized SHA-3 code.
- Eric
Powered by blists - more mailing lists