TRUSTED SECURITY MODULE (TSM) ATTESTATION REPORT INTERFACE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– Trusted Security Module (TSM) Attestation Report Interface πŸ’–

okay so bestie, welcome to the Trusted Secu...rt Interface(9) page from the Kernel API Manual 🫢 this is the TSM report interface, and it’s literally a common provider of blobs that facilitate attestation of a TVM (confidential computing guest) by an attestation service ✨

A TSM report combines a user-defined blob (likely a public-key with a nonce for a key-exchange protocol) with a signed attestation report πŸ”₯ that combined blob is then used to obtain secrets provided by an agent that can validate the attestation report πŸ‘‘

The expectation is that this interface is invoked infrequently, ngl. But configfs allows for multiple agents to own their own report generation instances to generate reports as often as needed πŸ’…

The attestation report format is TSM provider specific β€” when / if a standard materializes that can be published instead of the vendor layout 🌈 until then the 'provider' attribute indicates the format of 'outblob', and optionally

yes bestie, the source line really does stop at β€œand optionally” πŸ’€ no extra words, no cap.

πŸ‘€ SEE ALSO πŸ‘€

  • Kernel file ./drivers/virt/coco/guest/report.c

πŸ’Œ cute little sign-off: this page’s source/version is ./drivers/virt/coco/guest, and it’s dated October 2026. mwah πŸ’‹

πŸ“¦ where this page comes from