From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel@lists.01.org, "Jiewen Yao" <jiewen.yao@intel.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>
Subject: Re: Obtaining TCG final events on systems without TCG2 log support
Date: Fri, 14 Dec 2018 10:22:38 +0000 [thread overview]
Message-ID: <20181214102238.7hwrfj5dwxndphyy@srcf.ucam.org> (raw)
In-Reply-To: <4473c61d-6b34-b974-0d42-ec4bd51fb6db@redhat.com>
On Fri, Dec 14, 2018 at 10:32:29AM +0100, Laszlo Ersek wrote:
> On 12/13/18 19:55, Matthew Garrett wrote:
> > If a platform is unable to produce them in the final events table then
> > it's violating the spec.
>
> The question is why it's made impossible to comply with the spec if the
> platform only supports the 1.2 format.
If a platform can't implement the spec then the platform violates the
spec :)
> > If the platform only offers the 1.2 log format
> > then it seems reasonable to expect that the events in the final events
> > table would only contain a SHA1, but a TCG_PCR_EVENT2 structure that
> > only contains SHA1s isn't significantly more complicated than an old
> > style event.
> >
>
> OK... I guess that can be a valid interpretation. Would you please file
> a TianoCore BZ ticket about it, as a feature request?
Will do.
> (I'm assuming this isn't a regression, i.e., it's not the case that the
> feature used to work, but commit fd46e831bc33 regressed it.)
It looks like fd46e831bc33 didn't change anything significant here, so I
don't think this is a regression.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2018-12-14 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 1:17 Obtaining TCG final events on systems without TCG2 log support Matthew Garrett
2018-12-13 12:36 ` Laszlo Ersek
2018-12-13 13:23 ` Yao, Jiewen
2018-12-13 18:51 ` Matthew Garrett
2018-12-13 18:55 ` Matthew Garrett
2018-12-14 9:32 ` Laszlo Ersek
2018-12-14 10:09 ` Yao, Jiewen
2018-12-14 10:22 ` Matthew Garrett [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-list 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=20181214102238.7hwrfj5dwxndphyy@srcf.ucam.org \
--to=devel@edk2.groups.io \
/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