From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Daniel P. Smith" <dpsmith.dev@gmail.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
daniel.kiper@oracle.com, eric.snowberg@oracle.com,
javierm@redhat.com, jonmccune@google.com,
kanth.ghatraju@oracle.com, keng-yu.lin@hpe.com,
konrad.wilk@oracle.com, leif.lindholm@linaro.org,
phcoder@gmail.com, philip.b.tricca@intel.com,
ross.philipson@oracle.com, grub-devel@gnu.org
Subject: Re: TPM support within Grub2
Date: Tue, 17 Jul 2018 19:10:32 +0100 [thread overview]
Message-ID: <20180717181032.GA8927@srcf.ucam.org> (raw)
In-Reply-To: <671c05e8-b260-82a0-b54f-6da84f3d403b@gmail.com>
On Mon, Jul 16, 2018 at 12:33:42PM -0400, Daniel P. Smith wrote:
> On 07/16/2018 08:06 AM, Daniel Kiper wrote:
> > In general I am not against reorganization you are mentioning above.
> > Though I think that then you should rearange Matthew code and repost
> > it. Of course if Matthew does not object.
>
> I can align Matthew's code or if he would like, he is more than welcome
> to collaborate on the solution.
There's a lot of user demand for TPM2 support in grub, so my preference
would be:
1) Review and merge the verifiers framework
2) Update the current TPM2 code to match and review and merge that
3) Ensure that the functionality matches user expectations and then
develop a more generic midlayer based on that to support additional TPM
backends
My concern about doing (3) before (2) is that it may take multiple
attempts to develop something that works for us, and delay being able to
provide functionality that people would like to take advantage of. I
think some real-world use would make the process easier.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2018-07-17 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 23:09 TPM support within Grub2 Daniel P. Smith
2018-07-02 16:35 ` Daniel Kiper
2018-07-16 12:06 ` Daniel Kiper
2018-07-16 16:33 ` Daniel P. Smith
2018-07-17 13:04 ` Daniel Kiper
2018-07-17 17:22 ` Philip Tricca
2018-07-18 20:22 ` Daniel P. Smith
2018-07-17 18:10 ` Matthew Garrett [this message]
2018-07-18 9:03 ` Daniel Kiper
2018-07-18 16:08 ` Javier Martinez Canillas
2018-07-18 20:30 ` Daniel P. Smith
2018-07-20 11:37 ` Daniel Kiper
2018-07-17 16:57 ` Philip Tricca
2018-07-18 16:27 ` Javier Martinez Canillas
2018-07-18 20:39 ` Daniel P. Smith
2018-07-19 14:55 ` Philip Tricca
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=20180717181032.GA8927@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=daniel.kiper@oracle.com \
--cc=dkiper@net-space.pl \
--cc=dpsmith.dev@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=grub-devel@gnu.org \
--cc=javierm@redhat.com \
--cc=jonmccune@google.com \
--cc=kanth.ghatraju@oracle.com \
--cc=keng-yu.lin@hpe.com \
--cc=konrad.wilk@oracle.com \
--cc=leif.lindholm@linaro.org \
--cc=phcoder@gmail.com \
--cc=philip.b.tricca@intel.com \
--cc=ross.philipson@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.