public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Jeff Barnes <jeffbarnes@linux.microsoft.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: Restore sha384 and hmac_sha384 drbgs in FIPS mode
Date: Mon, 23 Jun 2025 17:25:23 +0800	[thread overview]
Message-ID: <aFkdgzg7J6MA1OhC@gondor.apana.org.au> (raw)
In-Reply-To: <20250617193005.1756307-1-jeffbarnes@linux.microsoft.com>

On Tue, Jun 17, 2025 at 03:30:05PM -0400, Jeff Barnes wrote:
> Set .fips_allowed in the following drbg alg_test_desc structs.
> 
> drbg_nopr_hmac_sha384
> drbg_nopr_sha384
> drbg_pr_hmac_sha384
> drbg_pr_sha384
> 
> The sha384 and hmac_sha384 DRBGs with and without prediction resistance
> were disallowed in an early version of the FIPS 140-3 Implementation
> Guidance document. Hence, the fips_allowed flag in struct alg_test_desc
> pertaining to the affected DRBGs was unset. The IG has been withdrawn
> and they are allowed again.
> 
> Furthermore, when the DRBGs are configured, /proc/crypto shows that
> drbg_*pr_sha384 and drbg_*pr_hmac_sha384 are fips-approved ("fips: yes")
> but because their self-tests are not run (a consequence of unsetting
> the fips_allowed flag), the drbgs won't load successfully with the seeming
> contradictory "fips: yes" in /proc/crypto.
> 
> This series contains a single patch that sets the fips_allowed flag in
> the sha384-impacted DRBGs, which restores the ability to load them in
> FIPS mode.
> 
> Link: https://lore.kernel.org/linux-crypto/979f4f6f-bb74-4b93-8cbf-6ed653604f0e@jvdsn.com/
> Link: https://csrc.nist.gov/CSRC/media/Projects/cryptographic-module-validation-program/documents/fips%20140-3/FIPS%20140-3%20IG.pdf
> 
> To: Herbert Xu <herbert@gondor.apana.org.au>
> To: David S. Miller <davem@davemloft.net>
> Cc: linux-crypto@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Jeff Barnes <jeffbarnes@linux.microsoft.com>
> ---
>  crypto/testmgr.c | 4 ++++
>  1 file changed, 4 insertions(+)

Patch applied.  Thanks.
-- 
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

      reply	other threads:[~2025-06-23  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 19:30 [PATCH] crypto: Restore sha384 and hmac_sha384 drbgs in FIPS mode Jeff Barnes
2025-06-23  9:25 ` 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=aFkdgzg7J6MA1OhC@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=davem@davemloft.net \
    --cc=jeffbarnes@linux.microsoft.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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