-
Notifications
You must be signed in to change notification settings - Fork 95
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
add: snp updates and mods to support VLEK #385
Conversation
Signed-off-by: Adrian Wobito <[email protected]>
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.
Looks great. I made some comments. Please add a commit message.
Also, is this PR really AWS specific or does it just add VLEK support?
Thanks again for the comments. Will work on this tomorrow and resolve the issues Greatly appreciate the review so quickly! |
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.
Welcome to the community @wobito ! Only some code style things and I also recommend that upstream first and then we can get this PR perfect and merge.
Signed-off-by: Adrian Wobito <[email protected]>
Signed-off-by: Adrian Wobito <[email protected]>
Signed-off-by: Adrian Wobito <[email protected]>
Signed-off-by: Adrian Wobito <[email protected]>
ark: &X509, | ||
asvk: &X509, | ||
) -> Result<X509> { | ||
let raw_vek = cert_chain |
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.
we might want to avoid introducing new abbreviations, since people will search for it and get confusing results. it's fine as a variable name, but in strings we can spell it out ("VCEK or VLEK not found") maybe.
I made the requested changes. I appreciate the quick feedback! :D still finding the sweet spot with rust ;P |
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.
small nit, otherwise lgtm
… endorsment key Signed-off-by: Adrian Wobito <[email protected]>
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.
Ok, looks really close to me. A couple small nits.
Signed-off-by: Adrian Wobito <[email protected]>
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.
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.
LGTM. Only one last thing
Signed-off-by: Adrian Wobito <[email protected]>
Wait, I think we need to update the evidence struct here still. |
Forgive me, but can you provide some more information so I can help in anyway |
afaiu in the corresponding guest-components change the evidence struct was modified, we need to do the same here, otherwise the evidence will not be parsed by the verifier. there is currently no CI job that would catch this. |
Thank you 🙏 I believe I understand that now |
Signed-off-by: Adrian Wobito <[email protected]>
Ok, I think we're good now. We do have a baremetal SNP runner that we could use for an e2e test in the future. |
that would be useful. the e2e tests themselves should not very invasive, but they do install a bunch of dependencies on the runner that might taint the machine. Maybe we can scrutinize this and run the tests in containers (privileged, w/ tee hw-devices mounted). |
This PR will add support for V{C|L}EK from amd snp-sev, this will also bump the sev crate from 1.2.0 to 3.1.1 with hope to close #286
Currently for the trustee sources to compile theazure-cvm-tooling
needed to have the sev crate bump as well, that is why there is a change in the cargo for those packages, this would need kinvolk/azure-cvm-tooling#52 to land before we can change the package back to it upstream provider.This was completed with the merge of kinvolk/azure-cvm-tooling#52
This pr also references a crate bump onsylabs/guest-components
until a patch can be contributed upstream there as well.This was completed with the merge of confidential-containers/guest-components#555