pRuntime: Manually encrypted worker privkey and gk master key #1370
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.
After a system reboot, some workers are no longer able to load their private keys. Upon investigation, we discovered that the CPU_SVN may change due to kernel updates or CPU firmware upgrades, which consequently breaks the Gramine encrypted file system.
This PR resolves the issue by abandoning the Gramine file system. Instead, we manually encrypt the keys using the MRENCLAVE sealing key. The CPU_SVN and ISV_SVN values are saved in the front of the encrypted file, allowing for the retrieval of the sealing key even after a firmware upgrade, using the previously stored CPU_SVN.
Tested:
@h4x3rotab @shelvenzhou This PR touches the critical part. Please review carefully.