Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set confidential UVM options during UVM start #1533

Merged
merged 1 commit into from
Oct 5, 2022

Conversation

anmaxvl
Copy link
Contributor

@anmaxvl anmaxvl commented Oct 1, 2022

To make the interface cleaner for cases when security policy isn't required, call to SetConfidentialUVMOptions within Start. 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 a security-policy-enforcer parameter.

Signed-off-by: Maksim An maksiman@microsoft.com

To make the interface cleaner for cases when security policy isn't
required, call to `SetConfidentialUVMOptions` within `Start`.
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 a `security-policy-enforcer`
parameter.

Signed-off-by: Maksim An <maksiman@microsoft.com>
@anmaxvl anmaxvl requested a review from a team as a code owner October 1, 2022 01:45
@anmaxvl anmaxvl merged commit 05b973d into microsoft:main Oct 5, 2022
@anmaxvl anmaxvl deleted the uvm-confidential-opts branch October 5, 2022 17:10
princepereira pushed a commit to princepereira/hcsshim that referenced this pull request Aug 29, 2024
To make the interface cleaner for cases when security policy isn't
required, call to `SetConfidentialUVMOptions` within `Start`.
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 a `security-policy-enforcer`
parameter.

Signed-off-by: Maksim An <maksiman@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants