All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: keyrings@vger.kernel.org, dhowells@redhat.com,
	zohar@linux.ibm.com, jarkko@kernel.org
Cc: nayna@linux.ibm.com, linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Stefan Berger <stefanb@linux.ibm.com>
Subject: [PATCH 0/2] Add support for ECDSA-signed kernel modules
Date: Tue,  6 Apr 2021 14:53:38 -0400	[thread overview]
Message-ID: <20210406185340.1079403-1-stefanb@linux.ibm.com> (raw)

This series adds support for ECDSA-signed kernel modules.

The first patch in this series attempts to address the issue where a
developer created an ECDSA key for signing modules and then falls back
to compiling an older version of the kernel that does not support
ECDSA keys. In this case this patch would delete that ECDSA key if it is
in certs/signing_key.pem and trigger the creation of an RSA key. However,
for this to work this patch would have to be applied to previous versions
of the kernel but would also only work for the developer if he/she used a
stable version of the kernel to which this patch was applied. So whether
this patch actually achieves the wanted effect is not always guaranteed.

The 2nd patch adds the support for the ECSDA-signed kernel modules.

This series depends on Nayna's series https://lkml.org/lkml/2021/3/30/571
and my ECDSA support series currently queued here:
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git/log/?h=ecc

  Stefan

Stefan Berger (2):
  certs: Trigger recreation of module signing key if it's not an RSA key
  certs: Add support for using elliptic curve keys for signing modules

 certs/Kconfig                         | 25 +++++++++++++++++++++++++
 certs/Makefile                        | 14 ++++++++++++++
 crypto/asymmetric_keys/pkcs7_parser.c |  4 ++++
 3 files changed, 43 insertions(+)

-- 
2.29.2


             reply	other threads:[~2021-04-06 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 18:53 Stefan Berger [this message]
2021-04-06 18:53 ` [PATCH 1/2] certs: Trigger recreation of module signing key if it's not an RSA key Stefan Berger
2021-04-06 18:53 ` [PATCH 2/2] certs: Add support for using elliptic curve keys for signing modules Stefan Berger
2021-04-07 15:53 ` [PATCH 0/2] Add support for ECDSA-signed kernel modules Jarkko Sakkinen
2021-04-07 16:10   ` Mimi Zohar
2021-04-07 17:53     ` Stefan Berger
2021-04-07 20:15       ` 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=20210406185340.1079403-1-stefanb@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=jarkko@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=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 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.