Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <7b29ae50e40a031fa145f12b5f5b31fb6578626e.camel@chronox.de>
Subject: Re: crypto: FIPS 200 mode
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>
Date:   Wed, 31 Mar 2021 09:51:07 +0200
In-Reply-To: <4e940d39-77c0-74d4-d282-216cc6030c11@infradead.org>
References: <4e940d39-77c0-74d4-d282-216cc6030c11@infradead.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

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.