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: Tue, 21 May 2019 20:30:33 -0400 [thread overview]
Message-ID: <1558485033.4039.215.camel@linux.ibm.com> (raw)
In-Reply-To: <cea244c1-f457-cdc0-e39b-c9381cb4dc79@linux.microsoft.com>
On Tue, 2019-05-21 at 10:48 -0700, Lakshmi wrote:
> On 5/14/19 3:07 PM, Lakshmi wrote:
> >>
> >> I should have asked you to make sure that the last 8 bytes of "X509v3
> >> Subject Key Identifier" in the certificate used to sign the kernel
> >> image is the same as above.
> >>
> >> Mimi
> >>
> >
> > Yes - the Subject Key Identifier matches the output from keyctl.
> >
> > Please see below:
> >
> > X509v3 Subject Key Identifier:
> >
> > 85:51:2D:09:FC:12:C7:F3:8B:96:79:35:26:51:DC:B3:65:90:33:36
>
> Please let me know if you need more information\logs on this issue.
Have you tried using "evmctl ima_verify" to verify the signature after
signing the file?
Perhaps it's something with the key. If you haven't already used the
scripts for generating the keys in the ima-evm-utils examples/
directory, you might try that.
I just pushed out the ima-evm-utils master branch. See if the new
"master" branch works.
Mimi
next prev parent reply other threads:[~2019-05-22 0:30 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 [this message]
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
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=1558485033.4039.215.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).