-
Notifications
You must be signed in to change notification settings - Fork 90
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
Bump kbs-types and kbs_protocol with a KBS protocol version change #445
Conversation
2b9aad2
to
934cdf1
Compare
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.
Thanks for this. I only have some opens due to compatibility.
The evidence
has been tranformed from string
into value
, which will give opportunity for combined attestation evidences like stated in confidential-containers/confidential-containers#176. Next phase we might need to think about to leverage this, e.g. once GPU attestation joins Trustee Bucket Meal.
@Xynnn007 I have opened an issue on kbs-types about this, but maybe we can also discuss it here. I suspect using serde_json on that type can lead to problems, because the internal representation of Is there any upside of using |
rebased and force-pushed due to some dependabot PRs being merged to avoid any merge conflicts. |
Just a reminder that the guest-components side of the same change is already merged and thus keeps some rcar client tests skipped. This also blocks the work with #242. Therefore, it would be good to get this merged. We can get back to virtee/kbs-types#43 once the discussion gets to a conclusion and |
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. Sorry for the delay. I was trying to find the tab.
kbs does guarantee backwards compatible functionality so only clients with exact protocol match are allowed. Signed-off-by: Mikko Ylinen <[email protected]>
This bumps kbs-types from 0.6.0 to 0.7.0 and kbs_protocol from guest-components to the latest HEAD. It's done in one commit to make the KBS protocol changes atomic. Signed-off-by: Mikko Ylinen <[email protected]>
KBS protocol version was bumped up to 0.1.1 so updating the spec accordingly. In addition, clarify the error handling of "request": also errors can happen, such as when the "request" version does not meet all the requirements. Signed-off-by: Mikko Ylinen <[email protected]>
Thanks! I have confirmed locally that the
|
Trustee bumped to version 0.1.1 in confidential-containers/trustee#445 , so update our initdata to match Signed-off-by: stevenhorsman <[email protected]>
Ref: confidential-containers/guest-components#628