From: Randy Dunlap <rdunlap@infradead.org>
To: Vladis Dronov <vdronov@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Simo Sorce <simo@redhat.com>
Subject: Re: [PATCH] crypto: fips - make proc files report fips module name and version
Date: Mon, 20 Jun 2022 14:15:00 -0700 [thread overview]
Message-ID: <23bc9020-4519-65ba-725e-e7efd226c192@infradead.org> (raw)
In-Reply-To: <20220620131618.952133-1-vdronov@redhat.com>
Hi--
On 6/20/22 06:16, Vladis Dronov wrote:
> diff --git a/crypto/Kconfig b/crypto/Kconfig
> index 1d44893a997b..082ff03d9f6c 100644
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -33,6 +33,27 @@ config CRYPTO_FIPS
> certification. You should say no unless you know what
> this is.
>
> +config CRYPTO_FIPS_NAME
> + string "FIPS Module Name"
> + default "Linux Kernel Cryptographic API"
> + depends on (CRYPTO_FIPS)
No parentheses.
> + help
> + This option sets the FIPS Module name reported by the Crypto API via
> + the /proc/sys/crypto/fips_name file.
> +
> +config CRYPTO_FIPS_CUSTOM_VERSION
> + bool "Use Custom FIPS Module Version"
> + depends on (CRYPTO_FIPS)
Ditto.
> + default n
> +
> +config CRYPTO_FIPS_VERSION
> + string "FIPS Module Version"
> + default "(none)"
> + depends on (CRYPTO_FIPS_CUSTOM_VERSION)
Ditto.
> + help
> + This option provides the ability to override the FIPS Module Version.
> + By default the KERNELRELEASE value is used.
--
~Randy
next prev parent reply other threads:[~2022-06-20 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:16 Vladis Dronov
2022-06-20 21:15 ` Randy Dunlap [this message]
2022-06-21 14:35 ` Vlad Dronov
2022-06-21 15:08 ` [PATCH v2] " Vladis Dronov
2022-06-27 1:19 ` Herbert Xu
2022-06-27 19:50 ` Vlad Dronov
2022-06-27 19:51 ` [PATCH v3] " Vladis Dronov
2022-07-08 7:20 ` Herbert Xu
2022-07-08 12:46 ` Vlad Dronov
2022-07-08 12:33 ` [PATCH v4] " Vladis Dronov
2022-07-15 8:49 ` 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=23bc9020-4519-65ba-725e-e7efd226c192@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simo@redhat.com \
--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
all inboxes | Powered by JetHome®