From: Mimi Zohar <zohar@linux.ibm.com>
To: Clay Chang <clayc@hpe.com>, linux-integrity@vger.kernel.org
Subject: Re: Question on signing the IMA signing key for kernel trusted keyrings?
Date: Thu, 16 Jan 2020 14:04:23 -0500 [thread overview]
Message-ID: <1579201463.5857.38.camel@linux.ibm.com> (raw)
In-Reply-To: <20200116183918.GA14177@blofly.tw.rdlabs.hpecorp.net>
On Fri, 2020-01-17 at 02:39 +0800, Clay Chang wrote:
> Hi,
>
> We know that IMA or EVM signing key must be signed by the .builtin_trusted_keys.
> In the .builtin_trusted_keys keyring of a fresh CentOS, for example,
> there are public keys created by CentOS. And the private key counterparts
> were not available publicly. So I think there is technically no way for
> others to sign the IMA or EVM key by the private keys of those CA.
>
> Is there a possibility of getting the IMA or EVM signing keys signed
> (probably by the public key in .builtin_trusted_keys) without rolling own
> CA and re-gen the kernel?
If the kernel was built with CONFIG_SYSTEM_EXTRA_CERTIFICATE, the
customer could insert their public key post build.[1] This would
obviously require the kernel to be resigned.
I agree there needs to be a simpler way of including a customer key,
without requiring them to resign the kernel.
Mimi
[1] c4c361059585 ("KEYS: Reserve an extra certificate symbol for
inserting without recompiling")
prev parent reply other threads:[~2020-01-16 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 18:39 Question on signing the IMA signing key for kernel trusted keyrings? Clay Chang
2020-01-16 19:04 ` Mimi Zohar [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=1579201463.5857.38.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=clayc@hpe.com \
--cc=linux-integrity@vger.kernel.org \
/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.