From: David Howells <dhowells@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dhowells@redhat.com, Stephan Mueller <smueller@chronox.de>,
linux-crypto@vger.kernel.org
Subject: Re: Adding SHAKE hash algorithms to SHA-3
Date: Mon, 15 Sep 2025 21:48:14 +0100 [thread overview]
Message-ID: <2767452.1757969294@warthog.procyon.org.uk> (raw)
In-Reply-To: <aMf_0xkJtcPQlYiI@gondor.apana.org.au>
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> I presume the algorithm choice is fixed, right?
I think so.
> If so you should be using lib/crypto.
Okay. That will automatically use CPU-optimised versions if available?
Btw, are the algorithms under crypto/ going to be switched to use the
implementations under lib/crypto/?
David
next prev parent reply other threads:[~2025-09-15 20:48 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 [this message]
2025-09-15 22:10 ` Eric Biggers
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=2767452.1757969294@warthog.procyon.org.uk \
--to=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