part2: Delay forward seal until VMs are not running #120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't run seal-system directly. The TPM interactions could have their MMIO data snooped. Instead we touch a marker file and let the delayed-seal initscript detect and run the forward seal at shutdown time. This is done when the VMs are not running, so we shouldn't have anyone around to snoop on the transaction. Signed-off-by: Jason Andryuk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Don't run seal-system directly. The TPM interactions could have their MMIO data snooped. Instead we touch a marker file and let the delayed-seal initscript detect and run the forward seal at shutdown time. This is done when the VMs are not running, so we shouldn't have anyone around to snoop on the transaction.
This PR is dependent on xenclient-oe PR#1493.