brintos

brintos / linux-shallow public Read only

0
0
Text · 5.6 KiB · 534408b Raw
146 lines · plain
1What:		/sys/kernel/config/tsm/report/$name/inblob2Date:		September, 20233KernelVersion:	v6.74Contact:	linux-coco@lists.linux.dev5Description:6		(WO) Up to 64 bytes of user specified binary data. For replay7		protection this should include a nonce, but the kernel does not8		place any restrictions on the content.9 10What:		/sys/kernel/config/tsm/report/$name/outblob11Date:		September, 202312KernelVersion:	v6.713Contact:	linux-coco@lists.linux.dev14Description:15		(RO) Binary attestation report generated from @inblob and other16		options The format of the report is implementation specific17		where the implementation is conveyed via the @provider18		attribute.19 20What:		/sys/kernel/config/tsm/report/$name/auxblob21Date:		October, 202322KernelVersion:	v6.723Contact:	linux-coco@lists.linux.dev24Description:25		(RO) Optional supplemental data that a TSM may emit, visibility26		of this attribute depends on TSM, and may be empty if no27		auxiliary data is available.28 29		When @provider is "sev_guest" this file contains the30		"cert_table" from SEV-ES Guest-Hypervisor Communication Block31		Standardization v2.03 Section 4.1.8.1 MSG_REPORT_REQ.32		https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/specifications/56421.pdf33 34What:		/sys/kernel/config/tsm/report/$name/manifestblob35Date:		January, 202436KernelVersion:	v6.1037Contact:	linux-coco@lists.linux.dev38Description:39		(RO) Optional supplemental data that a TSM may emit, visibility40		of this attribute depends on TSM, and may be empty if no41		manifest data is available.42 43		See 'service_provider' for information on the format of the44		manifest blob.45 46What:		/sys/kernel/config/tsm/report/$name/provider47Date:		September, 202348KernelVersion:	v6.749Contact:	linux-coco@lists.linux.dev50Description:51		(RO) A name for the format-specification of @outblob like52		"sev_guest" [1] or "tdx_guest" [2] in the near term, or a53		common standard format in the future.54 55		[1]: SEV Secure Nested Paging Firmware ABI Specification56		Revision 1.55 Table 2257		https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/specifications/56860.pdf58 59		[2]: Intel® Trust Domain Extensions Data Center Attestation60		Primitives : Quote Generation Library and Quote Verification61		Library Revision 0.8 Appendix 4,562		https://download.01.org/intel-sgx/latest/dcap-latest/linux/docs/Intel_TDX_DCAP_Quoting_Library_API.pdf63 64What:		/sys/kernel/config/tsm/report/$name/generation65Date:		September, 202366KernelVersion:	v6.767Contact:	linux-coco@lists.linux.dev68Description:69		(RO) The value in this attribute increments each time @inblob or70		any option is written. Userspace can detect conflicts by71		checking generation before writing to any attribute and making72		sure the number of writes matches expectations after reading73		@outblob, or it can prevent conflicts by creating a report74		instance per requesting context.75 76What:		/sys/kernel/config/tsm/report/$name/privlevel77Date:		September, 202378KernelVersion:	v6.779Contact:	linux-coco@lists.linux.dev80Description:81		(WO) Attribute is visible if a TSM implementation provider82		supports the concept of attestation reports for TVMs running at83		different privilege levels, like SEV-SNP "VMPL", specify the84		privilege level via this attribute.  The minimum acceptable85		value is conveyed via @privlevel_floor and the maximum86		acceptable value is TSM_PRIVLEVEL_MAX (3).87 88What:		/sys/kernel/config/tsm/report/$name/privlevel_floor89Date:		September, 202390KernelVersion:	v6.791Contact:	linux-coco@lists.linux.dev92Description:93		(RO) Indicates the minimum permissible value that can be written94		to @privlevel.95 96What:		/sys/kernel/config/tsm/report/$name/service_provider97Date:		January, 202498KernelVersion:	v6.1099Contact:	linux-coco@lists.linux.dev100Description:101		(WO) Attribute is visible if a TSM implementation provider102		supports the concept of attestation reports from a service103		provider for TVMs, like SEV-SNP running under an SVSM.104		Specifying the service provider via this attribute will create105		an attestation report as specified by the service provider.106		The only currently supported service provider is "svsm".107 108		For the "svsm" service provider, see the Secure VM Service Module109		for SEV-SNP Guests v1.00 Section 7. For the doc, search for110		"site:amd.com "Secure VM Service Module for SEV-SNP111		Guests", docID: 58019"112 113What:		/sys/kernel/config/tsm/report/$name/service_guid114Date:		January, 2024115KernelVersion:	v6.10116Contact:	linux-coco@lists.linux.dev117Description:118		(WO) Attribute is visible if a TSM implementation provider119		supports the concept of attestation reports from a service120		provider for TVMs, like SEV-SNP running under an SVSM.121		Specifying an empty/null GUID (00000000-0000-0000-0000-000000)122		requests all active services within the service provider be123		part of the attestation report. Specifying a GUID request124		an attestation report of just the specified service using the125		manifest form specified by the service_manifest_version126		attribute.127 128		See 'service_provider' for information on the format of the129		service guid.130 131What:		/sys/kernel/config/tsm/report/$name/service_manifest_version132Date:		January, 2024133KernelVersion:	v6.10134Contact:	linux-coco@lists.linux.dev135Description:136		(WO) Attribute is visible if a TSM implementation provider137		supports the concept of attestation reports from a service138		provider for TVMs, like SEV-SNP running under an SVSM.139		Indicates the service manifest version requested for the140		attestation report (default 0). If this field is not set by141		the user, the default manifest version of the service (the142		service's initial/first manifest version) is returned.143 144		See 'service_provider' for information on the format of the145		service manifest version.146