-
Notifications
You must be signed in to change notification settings - Fork 7
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 interface to allow user provided extensions #6
Comments
thomas-fossati
changed the title
Feature: Enhancement to decouple specific profile implementations from Base CoRIM and CoMID
Add interface to allow user provided extensions
Sep 16, 2021
Closing this as, now addressed using: |
deeglaze
added a commit
to deeglaze/corim
that referenced
this issue
Oct 25, 2024
Top level tags are not interpretable as a COSE object. Also 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 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
Problem Statement:
Present Implementation of Base CoRIM and CoMID has PSA specific types embedded into the base types.
One example is the Environment Type which has a Class Identifier object inside it.
One type of Class Identifier is the PSA Specific Implementation ID, which is PSA specific.
The issue it raises it:
Now any external library user uses the Class ID object will get the PSA specific Implementation ID as part of
the library implementation, which is not required.
Any new user of CoRIM, CoMID library, if they have their own ID types, will eventually pollute the library with their own types.
Solution
Additional context
None
The text was updated successfully, but these errors were encountered: