From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: linux-crypto@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org,
James.Bottomley@hansenpartnership.com, dhowells@redhat.com,
simo@redhat.com
Subject: Re: [PATCH v2 0/4] crypto: Add support for shake128/256 XOFs
Date: Fri, 18 Jul 2025 20:31:08 +1000 [thread overview]
Message-ID: <aHoibPpl7CHM3FGd@gondor.apana.org.au> (raw)
In-Reply-To: <20250630143834.2748285-1-stefanb@linux.ibm.com>
On Mon, Jun 30, 2025 at 10:38:30AM -0400, Stefan Berger wrote:
> 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
>
>
> v2:
> - Refactored crypto_shake_squeeze_bytes to be called for arbitrary number
> of bytes to return
> - Adjusted XOF test case parameters to better test modfied squeeze
> function
Please post this along with the actual user so that it can be
evaluated in the proper context.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2025-07-18 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 14:38 [PATCH v2 0/4] crypto: Add support for shake128/256 XOFs Stefan Berger
2025-06-30 14:38 ` [PATCH v2 1/4] crypto: Add squeeze function to shash_alg for support of XOFs Stefan Berger
2025-06-30 14:38 ` [PATCH v2 2/4] crypto: Add shake128/256 to generic sha3 module Stefan Berger
2025-06-30 14:38 ` [PATCH v2 3/4] crypto: Add tests cases for shake128 & shake256 to testmgr Stefan Berger
2025-06-30 14:38 ` [PATCH v2 4/4] crypto: Extend testmgr with tests for shake128/256 XOFs Stefan Berger
2025-07-18 10:31 ` Herbert Xu [this message]
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=aHoibPpl7CHM3FGd@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=James.Bottomley@hansenpartnership.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simo@redhat.com \
--cc=stefanb@linux.ibm.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).