go/common/node: Add runtime encryption key (REK) #5125
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Used attestation signature to authenticate the REK. When computing the signature the new version hashes also REK.
Next (optional) step would be to:
height
andsignature
toCapabilitiesTEE
,SGXAttestation
v2, andCapabilitiesTEE
.We would probably also need to introduce versioning for
CapabilitiesTEE
. As this step is more complicated and not needed, I decided to skip it.