On 10/26/22 7:24 AM, Daniel P. Berrangé wrote:
> On Tue, Oct 25, 2022 at 03:03:46PM -0400, Cole Robinson wrote:
>> On 10/17/22 3:42 AM, Michal Prívozník wrote:
>>> On 10/16/22 22:06, Cole Robinson wrote:
The value returned by qemu's query-sev-launch-measure comes
straight from the LAUNCH_
On Tue, Oct 25, 2022 at 03:03:46PM -0400, Cole Robinson wrote:
> On 10/17/22 3:42 AM, Michal Prívozník wrote:
> > On 10/16/22 22:06, Cole Robinson wrote:
> >> The value returned by qemu's query-sev-launch-measure comes
> >> straight from the LAUNCH_MEASURE SEV firmware command. It's two
> >> values
On 10/17/22 3:42 AM, Michal Prívozník wrote:
> On 10/16/22 22:06, Cole Robinson wrote:
>> The value returned by qemu's query-sev-launch-measure comes
>> straight from the LAUNCH_MEASURE SEV firmware command. It's two
>> values packed together: first 32 bytes is the launch measurement,
>> last 16 by
On 10/16/22 22:06, Cole Robinson wrote:
> The value returned by qemu's query-sev-launch-measure comes
> straight from the LAUNCH_MEASURE SEV firmware command. It's two
> values packed together: first 32 bytes is the launch measurement,
> last 16 bytes is the nonce.
>
> This combined value is reall
The value returned by qemu's query-sev-launch-measure comes
straight from the LAUNCH_MEASURE SEV firmware command. It's two
values packed together: first 32 bytes is the launch measurement,
last 16 bytes is the nonce.
This combined value is really just an artifact of the return value
of the firmwa
