Content Type in COSE_Sign1 out of spec #132
Comments
deeglaze
added a commit
to deeglaze/corim
that referenced
this issue
Oct 25, 2024
Top level tags are not interpretable as a COSE object. The protected header content-type is not meant to be application/rim+cbor according to the spec draft (Issue veraison#132). Support the spec's optional unsigned corim tag in COSE payload. Signed-off-by: Dionna Glaze <dionnaglaze@google.com>
deeglaze
added a commit
to deeglaze/corim
that referenced
this issue
Oct 29, 2024
Top level tags are not interpretable as a COSE object. The protected header content-type is not meant to be application/rim+cbor according to the spec draft (Issue veraison#132). Support the spec's optional unsigned corim tag in COSE payload. Signed-off-by: Dionna Glaze <dionnaglaze@google.com>
deeglaze
added a commit
to deeglaze/corim
that referenced
this issue
Oct 29, 2024
Top level tags are not interpretable as a COSE object. The protected header content-type is not meant to be application/rim+cbor according to the spec draft (Issue veraison#132). Support the spec's optional unsigned corim tag in COSE payload. Signed-off-by: Dionna Glaze <dionnaglaze@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
application/corim-unsigned+cbor is the expected content type, but signedcorim.go specifies application/rim+cbor.
The text was updated successfully, but these errors were encountered: