From: Herbert Xu <herbert@gondor.apana.org.au>
To: Vladis Dronov <vdronov@redhat.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Randy Dunlap <rdunlap@infradead.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Simo Sorce <simo@redhat.com>
Subject: Re: [PATCH v4] crypto: fips - make proc files report fips module name and version
Date: Fri, 15 Jul 2022 16:49:21 +0800 [thread overview]
Message-ID: <YtEqEYUZ4LH+dFS8@gondor.apana.org.au> (raw)
In-Reply-To: <20220708123313.119812-1-vdronov@redhat.com>
On Fri, Jul 08, 2022 at 02:33:13PM +0200, Vladis Dronov wrote:
> FIPS 140-3 introduced a requirement for the FIPS module to return
> information about itself, specifically a name and a version. These
> values must match the values reported on FIPS certificates.
>
> This patch adds two files to read a name and a version from:
>
> /proc/sys/crypto/fips_name
> /proc/sys/crypto/fips_version
>
> v2: removed redundant parentheses in config entries.
> v3: move FIPS_MODULE_* defines to fips.c where they are used.
> v4: return utsrelease.h inclusion
>
> Signed-off-by: Simo Sorce <simo@redhat.com>
> Signed-off-by: Vladis Dronov <vdronov@redhat.com>
> ---
> crypto/Kconfig | 21 +++++++++++++++++++++
> crypto/fips.c | 35 ++++++++++++++++++++++++++++++-----
> 2 files changed, 51 insertions(+), 5 deletions(-)
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
prev parent reply other threads:[~2022-07-15 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:16 [PATCH] " Vladis Dronov
2022-06-20 21:15 ` Randy Dunlap
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 [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=YtEqEYUZ4LH+dFS8@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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®