-
Currently we only support octet mode. While mail support is likely pointless, netascii could be helpful for transferring text files, although I doubt it. It's likely just worth doing to be a more comp…
-
## Describe the issue briefly
O3DE is perhaps the first major engine to assume shading to happen in ACEScg color space, but very little is written to explain them, things like potential performance…
-
**Describe the bug**
cbor_load returns CBOR_ERR_MALFORMATED upon receipt of all tags between 6 and 20 inclusive, including cose-sign1 (18) and cose-encrypt0 (16) in particular. The relevant code is i…
-
[RFC 8152 Section 8.1](https://datatracker.ietf.org/doc/html/rfc8152#section-8.1) require ECDSA to be deterministic.
> Implementations SHOULD use a deterministic version of ECDSA such as the one de…
-
Was found during the using cddl tools at https://github.com/ietf-teep/teep-protocol/issues/198.
Values for the bellow COSE_*_Tagged were undefined in the cddl file.
```
SUIT_Authentication_Bloc…
-
It would be nice if EdDSA curves were properly supported; and once supported, `webauthn_rs_proto::cose::COSEAlgorithm::secure_algs` added `COSEAlgorithm::EDDSA` to the returned `Vec`. Personally I wou…
-
Currently BRSKI-PRM relies on JSON-in-JWS for the exchanged objects, specifically regarding the voucher object.
In general, BRSKI-PRM is open to the requested voucher format as outlined in [sectio…
-
I'm opening this issue to discuss the `Key` design before cutting `v1.2.0` @setrofim (I've removed the tag and release you just created).
Extracted from https://github.com/veraison/go-cose/pull/146…
-
[General]
* Replace RFC 7049 with RFC 8949
* Replace RFC 8152 with RFC 9052 and RFC 9053
* When mentioning DTLS and referring to RFC 6347, refer also to RFC 9147
* As expected, the draft f…
-
I'm probably missing something but I don't see how to sign or verify with detached content, which RFC 8152 allows. (Reason: we are wondering whether to add COSE signing to GRASP, RFC 8990, and I'd lik…