Repository navigation
Conversation
Add --service-provider svsm and --manifest-path to fetch an SNP report and a separate raw manifest through configfs TSM. Preserve the report format and existing ioctl behavior, clean up request instances, and document the SVSM requirements. Validate CLI combinations, blob handling, and cleanup with unit tests. Signed-off-by: Ian Chin Wang <ian.chin.wang@oracle.com>
There was a problem hiding this comment.
Just a note, we're working on another tool in VirTEE: cvmtool, that uses configfs-tsm for reports in a vendor-agnostic way. Perhaps you would be more interested in that.
Co-authored-by: Tyler Fanelli <tfanelli@redhat.com> Signed-off-by: Ian Chin Wang <tom.icw@gmail.com>
Describe --service-provider generically and document SVSM as its currently supported value. Move the SVSM nonce, VMPL, and kernel requirements under the provider option and align the README usage and argument descriptions with the man page. Signed-off-by: Ian Chin Wang <ian.chin.wang@oracle.com>
Hi @tylerfanelli , thanks for bringing cvmtool to my attention. I understand there's a need to have a platform agnostic CLI for retrieving the certificates and the attestation reports. For future reference, do we prefer to deprecate |
Add --service-provider svsm and --manifest-path to fetch an SNP report and a separate raw manifest through configfs TSM. Preserve the report format and existing ioctl behavior, clean up request instances, and document the SVSM requirements.
Validate CLI combinations, blob handling, and cleanup with unit tests.