From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi <nramas@linux.microsoft.com>, linux-integrity@vger.kernel.org
Subject: Re: IMA signature generated by evmctl has unexpected key identifier
Date: Thu, 23 May 2019 09:26:01 -0400 [thread overview]
Message-ID: <1558617961.4347.161.camel@linux.ibm.com> (raw)
In-Reply-To: <3b8e6688-3d3e-18bf-239b-a0bc47d60a58@linux.microsoft.com>
On Wed, 2019-05-22 at 18:10 -0700, Lakshmi wrote:
> In my setup, IMA signing key will be signed by a key in the "BuiltIn
> Trusted Keys".
That is exactly how it is meant to be used. In conjunction with the
examples/ scripts, please follow the "Generate trusted keys" section
of the README. The last two steps show how to create a certificate
signing request (CSR) and sign the certificate with a CA key. The CA
public key should be loaded onto the builtin keyring.
Mimi
next prev parent reply other threads:[~2019-05-23 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 0:37 IMA signature generated by evmctl has unexpected key identifier nramas
2019-05-14 17:18 ` Lakshmi
2019-05-14 17:25 ` Mimi Zohar
2019-05-14 17:57 ` Lakshmi
2019-05-14 21:38 ` Mimi Zohar
2019-05-14 22:07 ` Lakshmi
2019-05-21 17:48 ` Lakshmi
2019-05-22 0:30 ` Mimi Zohar
2019-05-22 1:39 ` Lakshmi
2019-05-22 2:16 ` Lakshmi
2019-05-23 1:10 ` Lakshmi
2019-05-23 13:26 ` Mimi Zohar [this message]
2019-05-23 17:23 ` Lakshmi
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=1558617961.4347.161.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=nramas@linux.microsoft.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).