From: Eric Biggers <ebiggers@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>,
linux-crypto@vger.kernel.org
Subject: Re: Adding SHAKE hash algorithms to SHA-3
Date: Mon, 15 Sep 2025 17:10:55 -0500 [thread overview]
Message-ID: <20250915221055.GB286751@quark> (raw)
In-Reply-To: <2767452.1757969294@warthog.procyon.org.uk>
On Mon, Sep 15, 2025 at 09:48:14PM +0100, David Howells wrote:
> > If so you should be using lib/crypto.
>
> Okay. That will automatically use CPU-optimised versions if available?
If it's done properly, yes. It's already been done for various other
algorithms, such as SHA-1 and SHA-2. No one has done SHA-3 yet, but we
should.
> Btw, are the algorithms under crypto/ going to be switched to use the
> implementations under lib/crypto/?
Many already have, and most of the remaining ones should be as well.
- Eric
next prev parent reply other threads:[~2025-09-15 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 8:30 Adding SHAKE hash algorithms to SHA-3 David Howells
2025-09-15 12:00 ` Herbert Xu
2025-09-15 20:48 ` David Howells
2025-09-15 22:10 ` Eric Biggers [this message]
2025-09-19 6:41 ` David Howells
2025-09-19 13:57 ` Simo Sorce
2025-09-19 15:49 ` Stephan Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250915221055.GB286751@quark \
--to=ebiggers@kernel.org \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=smueller@chronox.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox