You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, we're evaluating GCS and this tooling, and we'd like for the workload containers to be able to retrieve a raw hardware attestation with a custom nonce/runtime_data, not just a OIDC token, so that the workload can quickly have HW-based assurance that it's running an a TEE.
One possible way of doing this would be to add another endpoint to the TEE Server (e.g., something like POST /v1/attestation). Another way would be to mount the appropriate kernel devices into the container; e.g., /dev/sev-guest, etc., but the latter seems more complex.
Hi there, we're evaluating GCS and this tooling, and we'd like for the workload containers to be able to retrieve a raw hardware attestation with a custom nonce/runtime_data, not just a OIDC token, so that the workload can quickly have HW-based assurance that it's running an a TEE.
One possible way of doing this would be to add another endpoint to the TEE Server (e.g., something like
POST /v1/attestation
). Another way would be to mount the appropriate kernel devices into the container; e.g.,/dev/sev-guest
, etc., but the latter seems more complex.https://github.com/google/go-tpm-tools/blob/main/launcher/teeserver/tee_server.go#L69
The text was updated successfully, but these errors were encountered: