[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZxqCNE-peVCmYus_@himmelriiki>
Date: Thu, 24 Oct 2024 20:21:56 +0300
From: Mikko Ylinen <mikko.ylinen@...ux.intel.com>
To: James Bottomley <James.Bottomley@...senpartnership.com>
Cc: "Xing, Cedric" <cedric.xing@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Samuel Ortiz <sameo@...osinc.com>, Lukas Wunner <lukas@...ner.de>,
Dionna Amalie Glaze <dionnaglaze@...gle.com>,
Qinkun Bao <qinkun@...gle.com>,
Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev
Subject: Re: [PATCH RFC 3/3] tsm: Add TVM Measurement Sample Code
On Sat, Sep 14, 2024 at 01:10:33PM -0400, James Bottomley wrote:
> On Sat, 2024-09-14 at 11:36 -0500, Xing, Cedric wrote:
>
> > Also, MRs are arch dependent and may also vary from gen to gen. I'm
> > afraid this might bring in more chaos than order.
>
> I think I understand this. All measurement registers are simply
> equivalent to PCRs in terms of the mathematical definition of how they
> extend. Exactly what measurements go into a PCR and how they are
Given this, would it be reasonable to go back to the digest based
input ABI idea where user space would use the TSM provider specifc
hash algo to prepare the input? The kernel eventlog for each MR (or
some notification mechanism to user space) would be provided just to
keep the digest ordering. Apps would map their inputs to that digest
list when doing attestation (in whatever format they choose).
On that note, we have the CCC kernel SIG call again Friday this week. If
we get enough people interested in this topic on the call, we could
brainstorm this a bit further.
-- Regards, Mikko
Powered by blists - more mailing lists