.@island-resort.com"
Cc: John Mattsson , Göran Selander
, "cose@ietf.org"
Subject: Re: [COSE] bstr wrapping for native signed (was Re: New Version
Notification for draft-mattsson-cose-cbor-cert-compress-05.txt)
Hi Laurence,
i don't have an implementation in higher languages such as
On 2020-12-15, at 21:46, Laurence Lundblade wrote:
>
> I mean modifying the decoder to return the offset (or some other access to
> to-be-hashed data). Not all, maybe only very few, return the offset. There is
> no need return it.
One valid use of CBOR is to prefix a single CBOR data item to
> On Dec 15, 2020, at 7:33 AM, Hristozov, Stefan
> wrote:
>
> What exactly do you mean by hacking the decoder? Do you mean to track the
> offset? What are the alternatives?
I mean modifying the decoder to return the offset (or some other access to
to-be-hashed data). Not all, maybe only
> On Dec 15, 2020, at 8:53 AM, Carsten Bormann wrote:
>
> On 2020-12-07, at 23:02, Laurence Lundblade wrote:
>>
>> I don’t think it works very well at all to directly sign encoded CBOR. It
>> should be wrapped in a byte string.
>
> Sorry for coming in late; I’m having a hard time following
On 2020-12-07, at 23:02, Laurence Lundblade wrote:
>
> I don’t think it works very well at all to directly sign encoded CBOR. It
> should be wrapped in a byte string.
Sorry for coming in late; I’m having a hard time following this thread.
Generally, we don’t want to do the “XMLDsig” thing and
Hi Laurence,
i don't have an implementation in higher languages such as Python or Go, so i
decided to code it today in Rust ( just for fun). Find my implementation
attached. I tested this implementation with test vector A.1.1.
I have a function called decode_native which returns a struct
Hi Laurence,
Thank you for your observations and comments!
I can't answer for what operations Stefan are using in his implementation,
but to continue discussing the possible solutions I'm interested in
clarifying the expectations on an off-the-shelf CBOR implementation:
When you talk about
Hi Laurence,
I’m aware of two implementation activities: by John (type 1) and by Stefan
(type 0).
Göran
On 2020-12-07, 23:02, "COSE" wrote:
I don’t think it works very well at all to directly sign encoded CBOR. It
should be wrapped in a byte string.
In particular issuerSignatureValue
