[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3030391.1BCLMh4Saa@tauon>
Date: Fri, 19 Sep 2025 23:20:28 +0200
From: Stephan Mueller <smueller@...onox.de>
To: Eric Biggers <ebiggers@...nel.org>
Cc: David Howells <dhowells@...hat.com>,
"Jason A. Donenfeld" <Jason@...c4.com>, Ard Biesheuvel <ardb@...nel.org>,
Harald Freudenberger <freude@...ux.ibm.com>,
Holger Dengler <dengler@...ux.ibm.com>,
Herbert Xu <herbert@...dor.apana.org.au>, Simo Sorce <simo@...hat.com>,
linux-crypto@...r.kernel.org, linux-s390@...r.kernel.org,
keyrings@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] lib/crypto: Add SHA3-224, SHA3-256, SHA3-384, SHA-512,
SHAKE128, SHAKE256
Am Freitag, 19. September 2025, 22:47:49 Mitteleuropäische Sommerzeit schrieb
Eric Biggers:
Hi Eric,
> Yes. But I'm still a bit puzzled why there suddenly seems to be
> interest in a FIPS pre-operational self-test for SHA-3 specifically.
> lib/ has had SHA-1 for two decades without a FIPS pre-operational
> self-test. If someone actually needs this, surely they would also need
> it, and have already needed it, for other algorithms?
I just answered on the FIPS requirements as I interpreted your question in
this regard. I am not saying it needs to be added here.
I am currently a bit confused between crypto vs lib/crypto with its FIPS vs
non-FIPS support. That, perhaps, contributed to my answer.
Ciao
Stephan
Powered by blists - more mailing lists