Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Stephan Müller" <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	Vladis Dronov <vdronov@redhat.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vladis Dronov <vdronov@redhat.com>
Subject: Re: [PATCH] crypto: testmgr - disallow certain DRBG hash functions in FIPS mode
Date: Tue, 17 Jan 2023 19:47:08 +0100	[thread overview]
Message-ID: <12136143.O9o76ZdvQC@positron.chronox.de> (raw)
In-Reply-To: <20230117172006.8912-1-vdronov@redhat.com>

Am Dienstag, 17. Januar 2023, 18:20:06 CET schrieb Vladis Dronov:

Hi Vladis,

> According to FIPS 140-3 IG, section D.R "Hash Functions Acceptable for
> Use in the SP 800-90A DRBGs", modules certified after May 16th, 2023
> must not support the use of: SHA-224, SHA-384, SHA512-224, SHA512-256,
> SHA3-224, SHA3-384. Disallow HMAC and HASH DRBGs using SHA-384 in FIPS
> mode.
> 
> Signed-off-by: Vladis Dronov <vdronov@redhat.com>

Thank you very much for the patch!

Reviewed-by: Stephan Müller <smueller@chronox.de>

> ---
> Some details:
> 
> The following DRBG algos are defined in testmgr.c as of now:
> 
> drbg_{no,}pr_ctr_aes128
> drbg_{no,}pr_ctr_aes192
> drbg_{no,}pr_ctr_aes256
> 
> drbg_{no,}pr_hmac_sha1
> drbg_{no,}pr_hmac_sha256
> drbg_{no,}pr_hmac_sha384 (disallow)
> drbg_{no,}pr_hmac_sha512
> 
> drbg_{no,}pr_sha1
> drbg_{no,}pr_sha256
> drbg_{no,}pr_sha384 (disallow)
> drbg_{no,}pr_sha512
> 
> Marked DRBGs should be disallowed in FIPS mode according to
> the requirements above.
> ---
>  crypto/testmgr.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/crypto/testmgr.c b/crypto/testmgr.c
> index 4476ac97baa5..fbb53d961ea9 100644
> --- a/crypto/testmgr.c
> +++ b/crypto/testmgr.c
> @@ -4782,7 +4782,6 @@ static const struct alg_test_desc alg_test_descs[] = {
> }, {
>  		/* covered by drbg_nopr_hmac_sha256 test */
>  		.alg = "drbg_nopr_hmac_sha384",
> -		.fips_allowed = 1,
>  		.test = alg_test_null,
>  	}, {
>  		.alg = "drbg_nopr_hmac_sha512",
> @@ -4805,7 +4804,6 @@ static const struct alg_test_desc alg_test_descs[] = {
> }, {
>  		/* covered by drbg_nopr_sha256 test */
>  		.alg = "drbg_nopr_sha384",
> -		.fips_allowed = 1,
>  		.test = alg_test_null,
>  	}, {
>  		.alg = "drbg_nopr_sha512",
> @@ -4841,7 +4839,6 @@ static const struct alg_test_desc alg_test_descs[] = {
> }, {
>  		/* covered by drbg_pr_hmac_sha256 test */
>  		.alg = "drbg_pr_hmac_sha384",
> -		.fips_allowed = 1,
>  		.test = alg_test_null,
>  	}, {
>  		.alg = "drbg_pr_hmac_sha512",
> @@ -4861,7 +4858,6 @@ static const struct alg_test_desc alg_test_descs[] = {
> }, {
>  		/* covered by drbg_pr_sha256 test */
>  		.alg = "drbg_pr_sha384",
> -		.fips_allowed = 1,
>  		.test = alg_test_null,
>  	}, {
>  		.alg = "drbg_pr_sha512",


Ciao
Stephan



  reply	other threads:[~2023-01-17 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 17:20 [PATCH] crypto: testmgr - disallow certain DRBG hash functions in FIPS mode Vladis Dronov
2023-01-17 18:47 ` Stephan Müller [this message]
2023-01-27 11:07 ` Herbert Xu

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=12136143.O9o76ZdvQC@positron.chronox.de \
    --to=smueller@chronox.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vdronov@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