Searched refs:attestation (Results 1 – 16 of 16) sorted by relevance
| /linux/Documentation/virt/coco/ |
| H A D | sev-guest.rst | 95 The SNP_GET_REPORT ioctl can be used to query the attestation report from the 97 provided by the SEV-SNP firmware to query the attestation report. 135 firmware to get the attestation report. 137 On success, the snp_ext_report_resp.data will contain the attestation report 174 reported TCB version in the attestation report. The command is similar 186 When requesting an attestation report a guest is able to specify whether 207 binaries will be measured as part of the SEV-SNP attestation report. 214 SEV-SNP attestation report. 223 Otherwise, guest owner attestation provides no assurance that the kernel wasn't
|
| H A D | tdx-guest.rst | 32 The TDX_CMD_GET_REPORT0 IOCTL can be used by the attestation software to get
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm_event_log.rst | 20 The main application for this is remote attestation and the reason why 25 therefore, attestation is typically more useful when the PCR contents
|
| H A D | tpm-security.rst | 101 endorsement certificate, creating an attestation identity key and 172 this is done, an attestation key (AK) is generated within the TPM and 183 based attestation process. The assumption here is that the 184 attestation is done by the TPM owner who thus has access to only the
|
| /linux/drivers/virt/coco/arm-cca-guest/ |
| H A D | Kconfig | 7 attestation report from the Realm Management Monitor(RMM).
|
| /linux/drivers/virt/coco/tdx-guest/ |
| H A D | Kconfig | 8 the TDX module to request the TDX guest details like attestation
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | amd-memory-encryption.rst | 164 of the memory contents that can be sent to the guest owner as an attestation 311 The KVM_SEV_GET_ATTESTATION_REPORT command can be used by the hypervisor to query the attestation 580 a guest attestation report, which will to allow userspace to provide a 582 that attestation report. 590 firmware at the time the attestation request is sent to SNP firmware. The 598 the attestation request is actually sent to firmware. To facilitate 602 after it finishes fetching the attestation request from firmware, at 614 the attestation request is actually issued. 635 certificates from userspace for each SNP attestation request the guest issues.
|
| /linux/Documentation/virt/ |
| H A D | ne_overview.rst | 77 These crypto measurements are included in a signed attestation document 80 the attestation doc.
|
| /linux/tools/arch/x86/intel_sdsi/ |
| H A D | intel_sdsi.c | 63 uint64_t attestation:1; member 278 …printf(" Attestation: %s\n", !!s->regs.en_features.attestation ? "Enabled" : "Di… in sdsi_read_reg()
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | maintainer-pgp-guide.rst | 706 Checking attestation on all messages, may take a moment...
|
| /linux/Documentation/security/ |
| H A D | snp-tdx-threat-model.rst | 202 authenticity is established via attestation.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-ima.rst | 6 (including the attestation service) interact with it - both during the
|
| /linux/drivers/misc/ |
| H A D | Kconfig | 525 measured boot flow. Userspace can use CDIs for remote attestation
|
| /linux/Documentation/translations/it_IT/process/ |
| H A D | maintainer-pgp-guide.rst | 839 Checking attestation on all messages, may take a moment...
|
| /linux/tools/arch/x86/kcpuid/ |
| H A D | cpuid.csv | 247 0x7, 0, edx, 1, sgx_keys , Intel SGX attestation services
|
| /linux/Documentation/virt/kvm/ |
| H A D | api.rst | 7431 i.e. has requested an attestation report from firmware, and would like the 7432 certificate data corresponding to the attestation report signature to be
|