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

VLEK: Adding ASVK Support #43

Merged
merged 1 commit into from
Mar 4, 2024
Merged

VLEK: Adding ASVK Support #43

merged 1 commit into from
Mar 4, 2024

Conversation

larrydewey
Copy link
Contributor

With the release of the VLEK, there is a separate api endpoint for requesting VLEK signing keys which are known as an AMD Signing VLEK Key (ASVK). This adds logic to handle these special use-cases. As the GHCB does not offer a unique GUID, assumptive logic must be applied to when the file should be named appropriately ASVK or ASK.

@larrydewey
Copy link
Contributor Author

CC @fitzthum

@larrydewey larrydewey force-pushed the vlek-pt2 branch 4 times, most recently from 68cf0a7 to 39744c8 Compare February 29, 2024 18:02
@larrydewey larrydewey marked this pull request as draft February 29, 2024 18:02
src/fetch.rs Show resolved Hide resolved
src/fetch.rs Outdated Show resolved Hide resolved
With the release of the VLEK, there is a separate
api endpoint for requesting VLEK signing keys which
are known as an AMD Signing VLEK Key (ASVK). This
adds logic to handle these special use-cases. As
the GHCB does not offer a unique UUID, assumptive
logic must be applied to when the file should be
named appropriately ASVK or ASK.

Signed-off-by: Larry Dewey <[email protected]>
@larrydewey larrydewey merged commit decb301 into virtee:main Mar 4, 2024
2 checks passed
@larrydewey larrydewey deleted the vlek-pt2 branch March 4, 2024 18:52
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.

5 participants