We need to make clear that a Resource Policy with an 'affirming' CPU section requires that the AS is configured with reference values for the right platforms.
Those reference values include the expected launch measurements.
Examples of sending SNP reference values to the RVPS:
https://github.com/kata-containers/kata-containers/pull/12191/files#diff-ff48cb2e0de04667da60ddff8920b131ce7b2ac8707899c3d660eb0a7d48653dR172-R186
The NVIDIA GPU doesn't require additional RVPS configuration. The GPU doesn't have the sort of user influenced launch variation that gets included in the CPU reports.
See feedback comment:
https://github.com/confidential-containers/confidentialcontainers.org/pull/152/files/aaaf5d1038edf1253182cbb23cdf26ad98bdaad7#r2718526873
See default CPU policy:
https://github.com/confidential-containers/trustee/blob/main/attestation-service/src/ear_token/ear_default_policy_cpu.rego
We need to make clear that a Resource Policy with an 'affirming' CPU section requires that the AS is configured with reference values for the right platforms.
Those reference values include the expected launch measurements.
Examples of sending SNP reference values to the RVPS:
https://github.com/kata-containers/kata-containers/pull/12191/files#diff-ff48cb2e0de04667da60ddff8920b131ce7b2ac8707899c3d660eb0a7d48653dR172-R186
The NVIDIA GPU doesn't require additional RVPS configuration. The GPU doesn't have the sort of user influenced launch variation that gets included in the CPU reports.
See feedback comment:
https://github.com/confidential-containers/confidentialcontainers.org/pull/152/files/aaaf5d1038edf1253182cbb23cdf26ad98bdaad7#r2718526873
See default CPU policy:
https://github.com/confidential-containers/trustee/blob/main/attestation-service/src/ear_token/ear_default_policy_cpu.rego