From: Mimi Zohar <zohar@linux.ibm.com>
To: Stefan Berger <stefanb@linux.ibm.com>,
Nayna Jain <nayna@linux.ibm.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org
Cc: linux-security-module@vger.kernel.org,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] keys: define build time generated ephemeral kernel CA key
Date: Thu, 11 Feb 2021 18:25:05 -0500 [thread overview]
Message-ID: <31d434e0861a02b214e3189f958921384aa75362.camel@linux.ibm.com> (raw)
In-Reply-To: <90213e4d-4c47-aec3-46f2-4b8e4ce0838f@linux.ibm.com>
On Thu, 2021-02-11 at 17:13 -0500, Stefan Berger wrote:
> On 2/11/21 2:54 PM, Nayna Jain wrote:
> > Certificates being loaded onto the IMA trusted keyring must be signed by
> > a key on either the builtin and secondary trusted keyring.
> >
> > This patch creates and includes in the kernel image an ephemeral CA
> > key, at build time when IMA_APPRAISE_MODSIG is enabled.
> >
> > Signed-off-by: Nayna Jain <nayna@linux.ibm.com>
> > ---
<snip>
> > diff --git a/certs/Makefile b/certs/Makefile
>
> > @@ -60,14 +78,23 @@ $(obj)/signing_key.pem: $(obj)/x509.genkey
> > @$(kecho) "### needs to be run as root, and uses a hardware random"
> > @$(kecho) "### number generator if one is available."
> > @$(kecho) "###"
> > +ifeq ($(CONFIG_IMA_APPRAISE_MODSIG),y)
> > + # Generate kernel build time CA Certificate.
> > + @$(Q)openssl req -new -nodes -utf8 \
> > + -$(CONFIG_MODULE_SIG_HASH) -days 36500 \
> > + -subj "/CN=Build time autogenerated kernel CA key" \
> > + -batch -x509 -config $(obj)/x509.genkey \
> > + -outform PEM -out $(CA_KEY) \
> > + -keyout $(CA_KEY) -extensions ca_ext \
> > + $($(quiet)redirect_openssl)
> > +endif # CONFIG_IMA_APPRAISE_MODSIG
> > $(Q)openssl req -new -nodes -utf8 \
> > -batch -config $(obj)/x509.genkey \
> > -outform PEM -out $(obj)/signing_key.csr \
> > -keyout $(obj)/signing_key.key -extensions myexts \
> > $($(quiet)redirect_openssl)
> > $(Q)openssl x509 -req -days 36500 -in $(obj)/signing_key.csr \
> > - -outform PEM -out $(obj)/signing_key.crt \
> > - -signkey $(obj)/signing_key.key \
> > + -outform PEM -out $(obj)/signing_key.crt $(SIGNER) \
> > -$(CONFIG_MODULE_SIG_HASH) -extensions myexts \
> > -extfile $(obj)/x509.genkey \
> > $($(quiet)redirect_openssl)
>
> It may make things easier (also below) if the CA was always created and
> the kernel signing key was always signed by that CA rather than doing
> this only in the IMA_APPRAISE_MODSIG case. Maybe someone else has an
> opinion on that?
Thanks, Stefan. It would definitely simplify the code. We wanted to
minimize the code change and solicit feedback, before making such a
change.
Mimi
next prev parent reply other threads:[~2021-02-11 23:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 19:54 [PATCH 0/5] ima: kernel build support for loading the kernel module signing key Nayna Jain
2021-02-11 19:54 ` [PATCH 1/5] keys: cleanup build time module signing keys Nayna Jain
2021-02-11 21:57 ` Stefan Berger
2021-02-12 21:33 ` Nayna
2021-02-12 23:47 ` Jarkko Sakkinen
2021-02-11 19:54 ` [PATCH 2/5] keys: generate self-signed module signing key using CSR Nayna Jain
2021-02-11 22:01 ` Stefan Berger
2021-02-18 22:02 ` Nayna
2021-02-12 23:47 ` Jarkko Sakkinen
2021-02-11 19:54 ` [PATCH 3/5] ima: update kernel module signing process during build Nayna Jain
2021-02-11 19:54 ` [PATCH 4/5] keys: define build time generated ephemeral kernel CA key Nayna Jain
2021-02-11 22:13 ` Stefan Berger
2021-02-11 23:25 ` Mimi Zohar [this message]
2021-02-12 3:30 ` kernel test robot
2021-02-12 8:25 ` kernel test robot
2021-02-11 19:54 ` [PATCH 5/5] ima: enable loading of build time generated key to .ima keyring Nayna Jain
2021-02-11 22:32 ` Stefan Berger
2021-02-12 23:48 ` 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=31d434e0861a02b214e3189f958921384aa75362.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--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 \
/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).