From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: jeyu@kernel.org, keyrings@vger.kernel.org, dhowells@redhat.com,
zohar@linux.ibm.com, nayna@linux.ibm.com,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key
Date: Wed, 28 Apr 2021 02:46:50 +0300 [thread overview]
Message-ID: <YIiiatWqrdBX0rPS@kernel.org> (raw)
In-Reply-To: <20210421194319.1489291-2-stefanb@linux.ibm.com>
On Wed, Apr 21, 2021 at 03:43:18PM -0400, Stefan Berger wrote:
> Address a kbuild issue where a developer created an ECDSA key for signing
> kernel modules and then builds an older version of the kernel, when bi-
> secting the kernel for example, that does not support ECDSA keys.
>
> Trigger the creation of an RSA module signing key if it is not an RSA key.
>
> Fixes: cfc411e7fff3 ("Move certificate handling to its own directory")
> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> ---
> certs/Makefile | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/certs/Makefile b/certs/Makefile
> index e3185c57fbd8..f64bc89ccbf1 100644
> --- a/certs/Makefile
> +++ b/certs/Makefile
> @@ -59,6 +59,11 @@ silent_redirect_openssl = 2>/dev/null
> # external private key, because 'make randconfig' might enable such a
> # boolean option and we unfortunately can't make it depend on !RANDCONFIG.
> ifeq ($(CONFIG_MODULE_SIG_KEY),"certs/signing_key.pem")
> +
> +X509TEXT=$(shell openssl x509 -in $(CONFIG_MODULE_SIG_KEY) -text)
> +
> +$(if $(findstring rsaEncryption,$(X509TEXT)),,$(shell rm -f $(CONFIG_MODULE_SIG_KEY)))
> +
> $(obj)/signing_key.pem: $(obj)/x509.genkey
> @$(kecho) "###"
> @$(kecho) "### Now generating an X.509 key pair to be used for signing modules."
> --
> 2.29.2
>
>
/Jarkko
next prev parent reply other threads:[~2021-04-27 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 19:43 [PATCH v3 0/2] Add support for ECDSA-signed kernel modules Stefan Berger
2021-04-21 19:43 ` [PATCH v3 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key Stefan Berger
2021-04-27 23:46 ` Jarkko Sakkinen [this message]
2021-04-21 19:43 ` [PATCH v3 2/2] certs: Add support for using elliptic curve keys for signing modules Stefan Berger
2021-04-27 23:46 ` Jarkko Sakkinen
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=YIiiatWqrdBX0rPS@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jeyu@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nayna@linux.ibm.com \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).