There's a comment in the corim Valid function that there can't be much done for validating Tag, but that isn't quite right since you can decode a RawTag and check the number for supported tags and continue down the tree. I started writing this up here https://github.com/veraison/corim/compare/main...deeglaze:corim:validatetag
Here's an error from the diff, with manually added formatting for clarity
I added the cbor.Tag{} deserialization's Content value for inspecting what could be going on here. There seems to be two different content value types associated with the psa.impl-id tag 600? Impl-id should just be 32 bytes without an interpretation the way it is in the environment-map, but here it's getting interpreted as maps when in an mkey.
I'm not sure how frequently y'all are updating static serialized cbor values in tests as the corim draft evolves, but this is confusing to me.
There's a comment in the corim Valid function that there can't be much done for validating Tag, but that isn't quite right since you can decode a RawTag and check the number for supported tags and continue down the tree. I started writing this up here https://github.com/veraison/corim/compare/main...deeglaze:corim:validatetag
Here's an error from the diff, with manually added formatting for clarity
I added the cbor.Tag{} deserialization's Content value for inspecting what could be going on here. There seems to be two different content value types associated with the psa.impl-id tag 600? Impl-id should just be 32 bytes without an interpretation the way it is in the environment-map, but here it's getting interpreted as maps when in an mkey.
I'm not sure how frequently y'all are updating static serialized cbor values in tests as the corim draft evolves, but this is confusing to me.