linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ken Goldman <kgold@linux.ibm.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>,
	linux-integrity@vger.kernel.org,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Matthew Garrett <mjg59@google.com>,
	Ken Goldman <kgoldman@us.ibm.com>
Subject: Re: Disparity in tpm pcr5 value
Date: Wed, 6 May 2020 10:12:49 -0400	[thread overview]
Message-ID: <4b3be2e9-35f7-d730-8e3b-b252ba5cb095@linux.ibm.com> (raw)
In-Reply-To: <20200505222731.whnkisag7tlrbcie@cantor>

On 5/5/2020 6:27 PM, Jerry Snitselaar wrote:
> On some systems we've had reports of the value of pcr5 doesn't match the 
> digests in the tpm event log.
> It looks like I'm able to reproduce here with 5.7-rc4 on a dell system 
> using this parser:
> 
> https://github.com/ValdikSS/binary_bios_measurements_parser
> 
> Any thoughts on where to start digging? Is there another tool I should 
> use to parse this?

If you email me the event log in binary, I can run it through the IBM 
calculator and see if I get the same error.



  reply	other threads:[~2020-05-06 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 22:27 Disparity in tpm pcr5 value Jerry Snitselaar
2020-05-06 14:12 ` Ken Goldman [this message]
2020-05-07  7:35   ` Jerry Snitselaar
2020-05-07 14:50     ` Mimi Zohar
2020-05-07 16:26       ` Jerry Snitselaar
2020-05-07 20:57         ` Mimi Zohar
2020-05-07 23:12           ` Jerry Snitselaar
2020-05-13 17:10 ` Jarkko Sakkinen
2020-05-13 17:59   ` Jerry Snitselaar
2020-05-14 11:03     ` Jarkko Sakkinen
2020-05-14 16:55       ` Jerry Snitselaar

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=4b3be2e9-35f7-d730-8e3b-b252ba5cb095@linux.ibm.com \
    --to=kgold@linux.ibm.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jsnitsel@redhat.com \
    --cc=kgoldman@us.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.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).