From: Stephan Mueller <smueller@chronox.de>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: crypto: FIPS 200 mode
Date: Wed, 31 Mar 2021 09:51:07 +0200 [thread overview]
Message-ID: <7b29ae50e40a031fa145f12b5f5b31fb6578626e.camel@chronox.de> (raw)
In-Reply-To: <4e940d39-77c0-74d4-d282-216cc6030c11@infradead.org>
Am Dienstag, dem 30.03.2021 um 15:26 -0700 schrieb Randy Dunlap:
>
> The Kconfig help text for CRYPTO_FIPS says
>
> config CRYPTO_FIPS
> bool "FIPS 200 compliance"
> ...
> help
> This option enables the fips boot option which is
> required if you want the system to operate in a FIPS 200
> certification. You should say no unless you know what
> this is.
>
> This seems confusing to me since it says "compliance" in one place and
> "certification" in another place. And AFAICT, those two words don't
> mean the same thing as far as NIST & FIPS are concerned.
>
>
> Should it say "compliance" in both places? E.g.
>
> help
> This option enables the fips boot option which is
> required if you want the system to operate in FIPS 200
> compliance mode. You should say no unless you know what
> this is.
Sounds good to me.
Ciao
Stephan
>
>
> thanks.
prev parent reply other threads:[~2021-03-31 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 22:26 Randy Dunlap
2021-03-31 7:51 ` Stephan Mueller [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=7b29ae50e40a031fa145f12b5f5b31fb6578626e.camel@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=rdunlap@infradead.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
all inboxes | Powered by JetHome®