From: Herbert Xu <herbert@gondor.apana.org.au>
To: Joachim Vandersmissen <git@jvdsn.com>
Cc: linux-crypto@vger.kernel.org, David Howells <dhowells@redhat.com>,
Simo Sorce <simo@redhat.com>,
Stephan Mueller <smueller@chronox.de>
Subject: Re: [PATCH v2 1/2] certs: Move RSA self-test data to separate file
Date: Wed, 1 May 2024 10:58:13 +0800 [thread overview]
Message-ID: <ZjGvxVKXu8JRc1bT@gondor.apana.org.au> (raw)
In-Reply-To: <b2787b62-fd1e-4815-a1c1-6b2d567ab977@jvdsn.com>
On Tue, Apr 30, 2024 at 09:52:44PM -0500, Joachim Vandersmissen wrote:
>
> I'm currently leaning towards adding FIPS_SIGNATURE_SELFTEST_RSA (and
> similarly FIPS_SIGNATURE_SELFTEST_ECDSA) as user-facing configuration
> options that depend on CRYPTO_RSA (and CRYPTO_ECDSA) and
> FIPS_SIGNATURE_SELFTEST. Then, it is up to the user to select the correct
> self-tests they need. It would still allow the user to create the same
> configuration "error" where FIPS_SIGNATURE_SELFTEST=y and
> FIPS_SIGNATURE_SELFTEST_RSA=m, but I think that users which care about
> FIPS_SIGNATURE_SELFTEST are doing it in the first place for FIPS compliance
> reasons. In that case, a FIPS laboratory should review the configuration to
> verify that the correct self-tests are executed at the correct time.
If the combo results in a crash then I think we have to fix it.
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:[~2024-05-01 2:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 5:42 [PATCH v2 1/2] certs: Move RSA self-test data to separate file Joachim Vandersmissen
2024-04-20 5:42 ` [PATCH v2 2/2] certs: Add ECDSA signature verification self-test Joachim Vandersmissen
2024-04-25 5:18 ` [PATCH v2 1/2] certs: Move RSA self-test data to separate file Herbert Xu
2024-05-01 2:52 ` Joachim Vandersmissen
2024-05-01 2:58 ` 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=ZjGvxVKXu8JRc1bT@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dhowells@redhat.com \
--cc=git@jvdsn.com \
--cc=linux-crypto@vger.kernel.org \
--cc=simo@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).