From: Simo Sorce <simo@redhat.com>
To: David Howells <dhowells@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] certs: Add FIPS self-test for signature verification
Date: Tue, 14 Jun 2022 10:15:24 -0400 [thread overview]
Message-ID: <831c7380f7d89fd8fb3a3043cf3b3d01001ae0be.camel@redhat.com> (raw)
In-Reply-To: <165515741424.1554877.9363755381201121213.stgit@warthog.procyon.org.uk>
On Mon, 2022-06-13 at 22:56 +0100, David Howells wrote:
> Hi Herbert,
>
> If you could look over this pair of patches? The second patch adds a simple
> selftest to allow the signature verification code so that it can be FIPS
> compliant. The first moves load_certificate_list() to the asymmetric key code
> to make this easier and renames it.
>
> I generated the test data myself, but I'm open to using some standard test
> data if you know of some; we don't want too much, however, as it's
> incompressible. Also, it has avoid blacklist checks on the keys it is using,
> lest the UEFI blacklist cause the selftest to fail.
>
> The patches can be found on the following branch:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-fixes
>
> David
> ---
> David Howells (2):
> certs: Move load_certificate_list() to be with the asymmetric keys code
> certs: Add FIPS selftests
>
>
> certs/Makefile | 4 +-
> certs/blacklist.c | 8 +-
> certs/common.c | 57 ------
> certs/common.h | 9 -
> certs/system_keyring.c | 6 +-
> crypto/asymmetric_keys/Kconfig | 10 +
> crypto/asymmetric_keys/Makefile | 2 +
> crypto/asymmetric_keys/selftest.c | 224 +++++++++++++++++++++++
> crypto/asymmetric_keys/x509_loader.c | 57 ++++++
> crypto/asymmetric_keys/x509_parser.h | 9 +
> crypto/asymmetric_keys/x509_public_key.c | 8 +-
> include/keys/asymmetric-type.h | 3 +
> 12 files changed, 321 insertions(+), 76 deletions(-)
> delete mode 100644 certs/common.c
> delete mode 100644 certs/common.h
> create mode 100644 crypto/asymmetric_keys/selftest.c
> create mode 100644 crypto/asymmetric_keys/x509_loader.c
>
>
Reviewed-by: Simo Sorce <simo@redhat.com>
--
Simo Sorce
RHEL Crypto Team
Red Hat, Inc
next prev parent reply other threads:[~2022-06-14 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 21:56 David Howells
2022-06-13 21:57 ` [PATCH 1/2] certs: Move load_certificate_list() to be with the asymmetric keys code David Howells
2022-06-13 21:57 ` [PATCH 2/2] certs: Add FIPS selftests David Howells
2022-06-27 7:16 ` Geert Uytterhoeven
2022-06-14 14:15 ` Simo Sorce [this message]
2022-06-15 4:20 ` [PATCH 0/2] certs: Add FIPS self-test for signature verification Herbert Xu
2022-06-15 22:34 ` David Howells
2022-06-16 8:47 ` 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=831c7380f7d89fd8fb3a3043cf3b3d01001ae0be.camel@redhat.com \
--to=simo@redhat.com \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--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
all inboxes | Powered by JetHome®