Re: [COSE] Key identifier of type bstr / int

[Ilari Liusvaara <[e-mail]>]

On Mon, Mar 21, 2022 at 02:13:50PM +0100, Laurence Lundblade wrote:
> Thinking about Mike’s comment today in COSE/Vienna about backwards
> compatibility. Looked at my code around this. That definitely seems
> like an issue. 
 
What does your code do if it encounters a recipient with int kid?

1. Treats the entiere message as malformed?
2. Ignores the recipient?
3. Something else? What?


And it is the implementations that do 1. (or 3. with some oddball
semantics) that worry me the most here. Not so much 2., as such
recipient is probably not correct anyway.



This also connects to the COSE-HPKE work: Where does one stick the
encapsulated ciphertext? It is naturally a bstr. It would seem natural
to stick it to the -1 (ephremeral key) field. Except that field is
defined to be a dictionary. However, this does not seem to stop editors'
copy from sticking a bstr to -1 field.



-Ilari