-
Enforce this in data validation.
RFC 7049 2.2.2
```
For indefinite-length byte strings, every data item (chunk) between
the indefinite-length indicator and the "break" MUST be a definite-
…
-
# Introduction
We will start writing the basic Checkbox from Chakra UI and start building on this later one by one.
## Checkbox to be built
![image](https://user-images.githubusercontent.com/…
-
UPDATED on Feb 14, 2020 to default to using CBOR Null when time tag isn't required and CBOR Undefined if time tag is required.
It would be helpful if 7049bis provided guidance on how to encode tagg…
-
The W3C Web Authentication work started with the JOSE stack and has since switched to the COSE stack. Moving Linked Data Proofs/Signatures to use COSE would bring us in line with the Web Authenticatio…
-
RFC 7049 test value -18446744073709551616 cannot fit into Go's int64, but it should still be added to the default corpus to make sure overflows like this are prevented.
The README.md should be upda…
-
Don't allow CBOR byte string (major type 2) as input to Go's Time.UnmarshalBinary.
Time values should only be encoded/decoded using these CBOR data types: pos or neg integer, float, and text stri…
-
# 🐞 Bug Report
### Affected Services
Metadata
### Is this a regression?
No
### Description and Minimal Reproduction
- Launch `device-virtual-go` (`./device-virtual`) where we are using a d…
-
This would help in scenarios where app/protocol specifies tag numbers 0 and 1 MUST be encoded but then provides an uninitialized/unspecified time value.
Unspecified/uninitialized time value creates…
-
Clarify that indefinite-length items with nothing inside are allowed, and are treated as empty data items (empty text strings, byte strings, arrays, and maps). In other words, clarify that the follow…
-
There are two issues with Section 9, which discusses how clients pass through unrecognized extensions.
1. In the algorithm for converting client extension inputs to CBOR, section 9 currently says:…