linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lakshmi <nramas@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.com>, linux-integrity@vger.kernel.org
Subject: Re: IMA signature generated by evmctl has unexpected key identifier
Date: Tue, 21 May 2019 18:39:26 -0700	[thread overview]
Message-ID: <c4637e97-7d7f-22da-fad2-b8ec4518c3e1@linux.microsoft.com> (raw)
In-Reply-To: <1558485033.4039.215.camel@linux.ibm.com>

On 5/21/19 5:30 PM, Mimi Zohar wrote:
> 
> Have you tried using "evmctl ima_verify" to verify the signature after
> signing the file?
Yes - I have. It fails with the following error. I have tried multiple 
signing keys, but no luck.

evmctl ima_verify --key /etc/keys/x509_evm.der /boot/vmlinuz-5.1.0-rc2+
/boot/vmlinuz-5.1.0-rc2+: RSA_public_decrypt() failed: -1
error:0407008A:rsa routines:RSA_padding_check_PKCS1_type_1:invalid padding
error:04067072:rsa routines:rsa_ossl_public_decrypt:padding check failed

> 
> 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'll give this a try.

Thanks,
  -lakshmi

  reply	other threads:[~2019-05-22  1:39 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 [this message]
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=c4637e97-7d7f-22da-fad2-b8ec4518c3e1@linux.microsoft.com \
    --to=nramas@linux.microsoft.com \
    --cc=linux-integrity@vger.kernel.org \
    --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).