From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <matthewgarrett@google.com>,
linux-integrity@vger.kernel.org
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, roberto.sassu@huawei.com,
linux-efi@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, tweek@google.com
Subject: Re: [PATCH V4 0/4] Add support for TCG2 event logs on EFI systems
Date: Tue, 26 Feb 2019 16:03:33 +0200 [thread overview]
Message-ID: <61db64b184a6b409248f5debb8549d6011a8cdac.camel@linux.intel.com> (raw)
In-Reply-To: <20190222202606.160816-1-matthewgarrett@google.com>
On Fri, 2019-02-22 at 12:26 -0800, Matthew Garrett wrote:
> This patchset adds support for obtaining the TCG2 format event log on
> EFI systems, along with support for copying up the final event log to
> capture events that occur after the primary log is obtained. V4 is
> identical to previous versions, except for tpm_read_log_efi() in patch 3
> being reworked to reduce nesting.
Looks good.
I'll re-try testing latter part of this weke.
/Jarkko
prev parent reply other threads:[~2019-02-26 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 20:26 [PATCH V4 0/4] Add support for TCG2 event logs on EFI systems Matthew Garrett
2019-02-22 20:26 ` [PATCH V4 1/4] tpm: Abstract crypto agile event size calculations Matthew Garrett
2019-02-22 20:26 ` [PATCH V4 2/4] tpm: Reserve the TPM final events table Matthew Garrett
2019-02-27 14:02 ` Jarkko Sakkinen
2019-02-27 19:57 ` Matthew Garrett
2019-02-28 12:38 ` Jarkko Sakkinen
2019-02-22 20:26 ` [PATCH V4 3/4] tpm: Append the final event log to the TPM event log Matthew Garrett
2019-02-22 20:26 ` [PATCH V4 4/4] efi: Attempt to get the TCG2 event log in the boot stub Matthew Garrett
2019-02-26 14:03 ` Jarkko Sakkinen [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=61db64b184a6b409248f5debb8549d6011a8cdac.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-efi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=peterhuewe@gmx.de \
--cc=roberto.sassu@huawei.com \
--cc=tweek@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).