-
Notifications
You must be signed in to change notification settings - Fork 16
tdx: allow limiting verification to explicit PIIDs #2048
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
Conversation
Do the documentation changes need to be backported?Changes to
|
|
f422c86 to
516be18
Compare
516be18 to
1df7b83
Compare
1df7b83 to
26b94a6
Compare
|
needs PR description |
26b94a6 to
0ddd817
Compare
|
All comments should be addressed now, ptal. |
thomasten
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed the first and the docs commit, which LGTM
This PR adds a new field to the TDX reference values,
AllowedPIIDs, that allows limiting the platform instance IDs (PIIDs) that are allowed by a manifest. Essentially, this can be used to only allow a specific, enumerated set of machines to participate in a Contrast deployment.If the list of allowed PIIDs is empty (the default), all TDX machines are allowed, making this change backwards-compatible.
Conceptually, this is closely related to #1952.