From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: Jessica Yu <jeyu@kernel.org>,
keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Mimi Zohar <zohar@linux.ibm.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Nayna Jain <nayna@linux.ibm.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stefan Berger <stefanb@linux.ibm.com>
Subject: Re: [PATCH v8 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key
Date: Wed, 30 Jun 2021 12:17:38 -0700 [thread overview]
Message-ID: <CAHk-=wgVZ6PUJ6Q=vqnhSkHnE2Rvr72xPFjoRU4=HHn-Rqxu4w@mail.gmail.com> (raw)
In-Reply-To: <20210629213421.60320-2-stefanb@linux.vnet.ibm.com>
On Tue, Jun 29, 2021 at 2:34 PM Stefan Berger
<stefanb@linux.vnet.ibm.com> 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.
Thanks, these two don't confuse me any more.
Linus
next prev parent reply other threads:[~2021-06-30 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 21:34 [PATCH v8 0/2] Add support for ECDSA-signed kernel modules Stefan Berger
2021-06-29 21:34 ` [PATCH v8 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key Stefan Berger
2021-06-30 19:17 ` Linus Torvalds [this message]
2021-07-02 6:49 ` Jarkko Sakkinen
2021-06-29 21:34 ` [PATCH v8 2/2] certs: Add support for using elliptic curve keys for signing modules Stefan Berger
2021-07-02 6:50 ` [PATCH v8 0/2] Add support for ECDSA-signed kernel modules 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='CAHk-=wgVZ6PUJ6Q=vqnhSkHnE2Rvr72xPFjoRU4=HHn-Rqxu4w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jarkko@kernel.org \
--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=stefanb@linux.vnet.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).