linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <matthewgarrett@google.com>
To: linux-integrity@vger.kernel.org
Cc: peterhuewe@gmx.de, jarkko.sakkinen@linux.intel.com, 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, bsz@semihalf.com
Subject: [PATCH V6 0/4] Add support for crypto agile TPM event logs
Date: Fri, 17 May 2019 14:39:14 -0700	[thread overview]
Message-ID: <20190517213918.26045-1-matthewgarrett@google.com> (raw)

Updated with the fixes from Bartosz and the header fixes folded in.
Bartosz, my machine still doesn't generate any final event log entries -
are you able to give this a test and make sure it's good?



             reply	other threads:[~2019-05-17 21:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 21:39 Matthew Garrett [this message]
2019-05-17 21:39 ` [PATCH V6 1/4] tpm: Abstract crypto agile event size calculations Matthew Garrett
2019-05-17 21:39 ` [PATCH V6 2/4] tpm: Reserve the TPM final events table Matthew Garrett
2019-05-17 21:39 ` [PATCH V6 3/4] tpm: Append the final event log to the TPM event log Matthew Garrett
2019-05-17 21:39 ` [PATCH V6 4/4] efi: Attempt to get the TCG2 event log in the boot stub Matthew Garrett
2019-05-18 16:12   ` Ard Biesheuvel
2019-05-20 17:37 ` [PATCH V6 0/4] Add support for crypto agile TPM event logs Bartosz Szczepanek

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=20190517213918.26045-1-matthewgarrett@google.com \
    --to=matthewgarrett@google.com \
    --cc=bsz@semihalf.com \
    --cc=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=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).