microsoft / azure-privacy-sandbox-kms

MIT License
4 stars 6 forks source link

`/keyReleasePolicy` returns potentially unexpected values #176

Open DomAyre opened 3 days ago

DomAyre commented 3 days ago

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