Re: [PATCH v3 0/4] tdx-guest: Make Quote buffer size dynamic
Peter Fang <[email protected]>
| Newsgroups | org.kernel.vger.linux-kernel,dev.linux.lists.linux-coco,org.kernel.vger.kvm |
|---|---|
| Message-ID | <20260812232714.GE1013044@pedri> |
On Wed, Aug 12, 2026 at 03:47:28PM -0700, Edgecombe, Rick P wrote: > On Wed, 2026-08-12 at 15:37 -0700, Peter Fang wrote: > > > > > > But part of this too, is that "DICE" is an industry standard [0]. Some of > > > the existing TDX attestation format is TDX specific, and moving to the > > > standard is expected to make the verifier better. So TDX does not have full > > > flexibility in choosing which bits go where. There is some. But I'm not sure > > > which. > > > > In the SGX era, a lot of this attestation stuff was Intel proprietary > > and that caused a lot of pain. To follow the DICE standard the bits in > > the report have specific places to go inside the quote blob. IOW the > > DICE quote doesn't just carry the report like an attachment, and so the > > two can't be separated (not without breaking the standard in some way). > > Yea that was my suspicion. I'm not sure if separating them was really Sean's > understanding or not. But the other part is that the verifiers and other VMM > infrastructures are already expecting this standard format. It would have a lot > of downsides. > > But the "grow the report" or "grow the report and quote" are still options that > leave the quote in the expected DICE format, right? Sean I'll assume you still Yes, the final quote will be the same, in DICE format. > prefer the "grow both" option for the sake of kicking the quoting > responsibilities out of KVM. If so, let's see if Dave can weigh in.