All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Howells <dhowells@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Simo Sorce <simo@redhat.com>, Jarkko Sakkinen <jarkko@kernel.org>,
	keyrings@vger.kernel.org,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] certs: Add FIPS selftests
Date: Mon, 27 Jun 2022 09:16:59 +0200	[thread overview]
Message-ID: <CAMuHMdWWtdoAwWo_qitV+s-3amxKzbVSDJ3f51E9fKT3MQwLAw@mail.gmail.com> (raw)
In-Reply-To: <165515742832.1554877.2073456606206090838.stgit@warthog.procyon.org.uk>

Hi David,

On Tue, Jun 14, 2022 at 12:29 AM David Howells <dhowells@redhat.com> wrote:
> Add some selftests for signature checking when FIPS mode is enabled.  These
> need to be done before we start actually using the signature checking for
> things and must panic the kernel upon failure.
>
> Note that the tests must not check the blacklist lest this provide a way to
> prevent a kernel from booting by installing a hash of a test key in the
> appropriate UEFI table.
>
> Reported-by: Simo Sorce <simo@redhat.com>
> Signed-off-by: David Howells <dhowells@redhat.com>

Thanks for your patch, which is now commit 3cde3174eb910513 ("certs:
Add FIPS selftests") in v5.19-rc4.

> --- a/crypto/asymmetric_keys/Kconfig
> +++ b/crypto/asymmetric_keys/Kconfig
> @@ -75,4 +75,14 @@ config SIGNED_PE_FILE_VERIFICATION
>           This option provides support for verifying the signature(s) on a
>           signed PE binary.
>
> +config FIPS_SIGNATURE_SELFTEST
> +       bool "Run FIPS selftests on the X.509+PKCS7 signature verification"

Is there any reason this cannot be tristate, so I can always enable
this as a module, and run the test by loading the module whenever
I want?

> +       help
> +         This option causes some selftests to be run on the signature
> +         verification code, using some built in data.  This is required
> +         for FIPS.
> +       depends on KEYS
> +       depends on ASYMMETRIC_KEY_TYPE
> +       depends on PKCS7_MESSAGE_PARSER
> +

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2022-06-27  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 21:56 [PATCH 0/2] certs: Add FIPS self-test for signature verification 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 [this message]
2022-06-14 14:15 ` [PATCH 0/2] certs: Add FIPS self-test for signature verification Simo Sorce
2022-06-15  4:20 ` 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=CAMuHMdWWtdoAwWo_qitV+s-3amxKzbVSDJ3f51E9fKT3MQwLAw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --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 \
    --cc=simo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.