-
RFC 8949 obsoletes RFC 7049, and the latter is what System.Formats.Cbor is built from.
The revised RFC changes, subtly, the sorting of map keys. The new RFC uses lexicographic sorting, as noted in …
-
![Screenshot-2022-02-08-18:45:45](https://user-images.githubusercontent.com/20933385/153034560-71df1522-795c-4e71-aa3f-fa6b903db74b.png)
While, [RFC8948](https://datatracker.ietf.org/doc/html/rfc89…
-
https://cbor.io cites this repo saying "supports everything mentioned in RFC 7049".
A new edition of RFC 7049 has become available as [RFC 8949](https://www.rfc-editor.org/rfc/rfc8949.html).
While t…
-
Related to #953 .
Currently we specify that map keys must be sorted in the binary encoding, although we don't actually specify *how* they are sorted, this is presumably in lexicographic order of th…
-
The [RFC 8949](https://datatracker.ietf.org/doc/html/rfc8949) describes the Concise Binary Object Representation (CBOR). It's a data format whose design goals include the possibility of extremely smal…
-
I've stumbled over your VPack and see your comparisons to other serialization formats. I'm just wondering how VPack compares to CBOR (http://cbor.io/), which in the meantime is even "standardized" in …
-
@lieunguyen-tma go-dots is using a CBOR library that could exhaust memory in 1 decode attempt of 9-10 bytes of malformed data.
### Relevant Code
go-dots/dots_common/messages/message.go
```
i…
-
When decoding a map that was encoded as an `OrderedDict`, the resulting map is a standard python `dict` which does not guarantee ordering. I don't believe ordered maps are part of RFC 7049, but it may…
-
#### Summary
Attempting to decode 9-10 bytes of malformed CBOR data (BinaryJWTClaims) causes
"fatal error: out of memory" or "runtime: out of memory" errors.
Only 1 decode attempt is needed …
-
Hi,
Currently specification doesn't include version and/or published date. May I ask if you could do so?
Just for example, one format CBOR has [details](https://tools.ietf.org/html/rfc7049) abou…
ghost updated
4 years ago