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

Update Response struct to follow RFC 7516 #44

Merged
merged 2 commits into from
Nov 29, 2024

Conversation

Xynnn007
Copy link
Contributor

The original KBS Protocol's Response follows RFC7519's JWE definition. Now it is lacked of aad field for AEAD. Also, this patch adds the definition for ProtectedHeader due to the RFC.

Due to RFC 7516, if AEAD is used in JWE, `aad` must be included to JSON
serialization of the JWE. See

https://datatracker.ietf.org/doc/html/rfc7516#section-7.2.1

Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
The struct of the ProtectedHeader is actually well defined in RFC7519,
the changing from string to a struct would do help to serialization and
deserialization.

See https://datatracker.ietf.org/doc/html/rfc7516

Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
Copy link
Member

@tylerfanelli tylerfanelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Will the KBS documentation be updated to show this?

@Xynnn007
Copy link
Contributor Author

LGTM. Will the KBS documentation be updated to show this?

Yes. I will update this in confidential-containers/trustee#597 then

@tylerfanelli tylerfanelli merged commit f313edb into virtee:main Nov 29, 2024
3 checks passed
@Xynnn007 Xynnn007 deleted the fix-jwe branch November 29, 2024 23:55
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.

3 participants