set confidential UVM options during UVM start #1533
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.
To make the interface cleaner for cases when security policy isn't required, call to
SetConfidentialUVMOptions
withinStart
. When no enforcer or policy are supplied GCS will initialize an open door enforcer.UtilityVM object now holds the confidential options to use them during
Start
.By default the UVM reference is expected to be located at the directory as the shim executable rather than under linux boot files. This has been done to avoid holding this information on the UVM object.
uvmboot
has been updated to take asecurity-policy-enforcer
parameter.Signed-off-by: Maksim An maksiman@microsoft.com