[svsm-devel] Attest multiple services guid byte order

[Dionna Amalie Glaze]

Hi folks, one more request for clarification, since providing attest
single service necessitates providing attest_services to be compliant
with the spec.

The GUID table that is communicated for auxblob (certificates from the
host) has been clarified to be in big endian order, whereas the
service_guid for SVSM has been clarified to be in little endian order.

For the GUID table format parsers written for auxblob to be reusable
for manifestblob, I'd like to recommend that we output big endian
order.
The general idea would be that guids are consumed in native order and
produced in network order.

Any objection to this?

-- 
-Dionna Glaze, PhD, CISSP, CCSP (she/her)