We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To mitigate attacks described in the X.509 IETF RFC here, we should add something like the following language:
If x5c is the in unprotected header or was received out-of-band, the verifier MUST check the x5t protected header.
x5c
x5t
Note that COSE has this language built in, but JOSE leaves that open.
The text was updated successfully, but these errors were encountered:
Noting that the current text requires using x5c and says nothing about protected vs. unprotected
https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-04.html#name-issuer-signed-jwt-verificat
Sorry, something went wrong.
No branches or pull requests
To mitigate attacks described in the X.509 IETF RFC here, we should add something like the following language:
If
x5c
is the in unprotected header or was received out-of-band, the verifier MUST check thex5t
protected header.Note that COSE has this language built in, but JOSE leaves that open.
The text was updated successfully, but these errors were encountered: