linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: jeyu@kernel.org, keyrings@vger.kernel.org, dhowells@redhat.com,
	dwmw2@infradead.org, 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 v6 0/4] Add support for ECDSA-signed kernel modules
Date: Mon, 14 Jun 2021 22:21:39 +0300	[thread overview]
Message-ID: <20210614192139.vt5eggy6gq52ljce@kernel.org> (raw)
In-Reply-To: <20210614191948.io4waff5aisah36q@kernel.org>

On Mon, Jun 14, 2021 at 10:19:51PM +0300, Jarkko Sakkinen wrote:
> On Thu, Jun 10, 2021 at 08:56:19AM -0400, Stefan Berger wrote:
> > This series adds support for ECDSA-signed kernel modules. It also
> > attempts to 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 bisecting the kernel for example, that does not support
> > ECDSA keys.
> > 
> > The first patch addresses the kbuild issue of needing to 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
> > backported 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 patch depends on the ECDSA support series currently queued here:
> > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git/log/?h=ecc
> > 
> >   Stefan
> > 
> > v6:
> >   - Patch 2/4 is fixing V4's 1/2 and 4/4 is fixing V4's 2/2. Both fixup
> >     patches to be squashed.
> > 
> > v5:
> >   - do not touch the key files if openssl is not installed; likely
> >     addresses an issue pointed out by kernel test robot
> > 
> > v4:
> >   - extending 'depends on' with MODULES to (IMA_APPRAISE_MODSIG && MODULES)
> >   
> > v3: - added missing OIDs for ECDSA signed hashes to pkcs7_sig_note_pkey_algo
> >   - added recommendation to use string hash to Kconfig help text
> > 
> > v2:
> >   - Adjustment to ECDSA key detector string in 2/2
> >   - Rephrased cover letter and patch descriptions with Mimi
> > 
> > 
> > Stefan Berger (4):
> >   certs: Trigger creation of RSA module signing key if it's not an RSA
> >     key
> >   certs: Check whether openssl tool is available
> >   certs: Add support for using elliptic curve keys for signing modules
> >   certs: Adjustment due to 'Check whether openssl tool is available'
> > 
> >  certs/Kconfig                         | 26 ++++++++++++++++++++++++++
> >  certs/Makefile                        | 21 +++++++++++++++++++++
> >  crypto/asymmetric_keys/pkcs7_parser.c |  8 ++++++++
> >  3 files changed, 55 insertions(+)
> > 
> > -- 
> > 2.29.2
> > 
> > 
> 
> Since you know the commit ID's in
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
> 
> you could just use fixes-tags and send exactly two patch series. Works
> better with various tools (e.g. https://pypi.org/project/b4/)

And also since then existence of ancestors is guaranteed.

/Jarkko

      parent reply	other threads:[~2021-06-14 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 12:56 [PATCH v6 0/4] Add support for ECDSA-signed kernel modules Stefan Berger
2021-06-10 12:56 ` [PATCH v6 1/4] certs: Trigger creation of RSA module signing key if it's not an RSA key Stefan Berger
2021-06-10 12:56 ` [PATCH v6 2/4] certs: Check whether openssl tool is available Stefan Berger
2021-06-10 12:56 ` [PATCH v6 3/4] certs: Add support for using elliptic curve keys for signing modules Stefan Berger
2021-06-10 12:56 ` [PATCH v6 4/4] certs: Adjustment due to 'Check whether openssl tool is available' Stefan Berger
2021-06-14 19:23   ` Jarkko Sakkinen
2021-06-14 19:28     ` Stefan Berger
2021-06-15 13:06       ` Jarkko Sakkinen
2021-06-15 13:29         ` Stefan Berger
2021-06-18  9:04           ` Jarkko Sakkinen
2021-06-10 12:59 ` [PATCH v6 0/4] Add support for ECDSA-signed kernel modules Stefan Berger
2021-06-14 19:19 ` Jarkko Sakkinen
2021-06-14 19:20   ` Stefan Berger
2021-06-15 13:05     ` Jarkko Sakkinen
2021-06-14 19:21   ` Jarkko Sakkinen [this message]

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=20210614192139.vt5eggy6gq52ljce@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.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=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).