From: Stefan Berger <stefanb@linux.ibm.com>
To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net
Cc: linux-kernel@vger.kernel.org,
James.Bottomley@HansenPartnership.com, dhowells@redhat.com,
simo@redhat.com, Stefan Berger <stefanb@linux.ibm.com>
Subject: [RFC PATCH 0/4] crypto: Add support for shake128/256 XOFs
Date: Mon, 23 Jun 2025 09:18:26 -0400 [thread overview]
Message-ID: <20250623131830.2194643-1-stefanb@linux.ibm.com> (raw)
This series adds support for shake128/256 extended output functions (XOFs)
along with test cases to verify the produced digest and XOF output. A new
squeeze method is added to the shash_alg structure to get an arbitrary
number of bytes from these XOFs.
Regards,
Stefan
Stefan Berger (4):
crypto: Add squeeze function to shash_alg for support of XOFs
crypto: Add shake128/256 to generic sha3 module
crypto: Add tests cases for shake128 & shake256 to testmgr
crypto: Extend testmgr with tests for shake128/256 XOFs
crypto/hash_info.c | 4 +
crypto/sha3_generic.c | 211 +++++++++++++
crypto/shash.c | 9 +
crypto/testmgr.c | 72 +++++
crypto/testmgr.h | 522 +++++++++++++++++++++++++++++++++
include/crypto/algapi.h | 2 +-
include/crypto/hash.h | 25 +-
include/crypto/sha3.h | 19 ++
include/uapi/linux/hash_info.h | 2 +
9 files changed, 862 insertions(+), 4 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-23 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:18 Stefan Berger [this message]
2025-06-23 13:18 ` [RFC PATCH 1/4] crypto: Add squeeze function to shash_alg for support of XOFs Stefan Berger
2025-06-23 13:18 ` [RFC PATCH 2/4] crypto: Add shake128/256 to generic sha3 module Stefan Berger
2025-06-23 13:18 ` [RFC PATCH 3/4] crypto: Add tests cases for shake128 & shake256 to testmgr Stefan Berger
2025-06-23 13:18 ` [RFC PATCH 4/4] crypto: Extend testmgr with tests for shake128/256 XOFs Stefan Berger
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=20250623131830.2194643-1-stefanb@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simo@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).