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

/keyReleasePolicy returns potentially unexpected values #176

Open
Tracked by #166
DomAyre opened this issue Oct 23, 2024 · 0 comments
Open
Tracked by #166

/keyReleasePolicy returns potentially unexpected values #176

DomAyre opened this issue Oct 23, 2024 · 0 comments

Comments

@DomAyre
Copy link
Collaborator

DomAyre commented Oct 23, 2024

I'm not an expert here, but I've just added a test which adds and then removes the key release policy, when I do that and query the current policy I get something which only looks half removed?

# Add policy
policy-added:{'type': 'add', 'claims': {'x-ms-ver': ['2', '3'], 'x-ms-sevsnpvm-smt-allowed': [True], 'x-ms-sevsnpvm-is-debuggable': [False]}, 'gte': {'x-ms-ver': '2'}, 'gt': {'x-ms-ver': '1'}}

# Remove policy
policy-removed:{'type': 'add', 'claims': {'x-ms-sevsnpvm-smt-allowed': [True], 'x-ms-sevsnpvm-is-debuggable': [False]}, 'gte': {}, 'gt': {}}

This is complicated by #175 because I don't know what the default key release policy is

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

No branches or pull requests

1 participant