-
Section 7.2 says:
> When the ProcessTeepMessage API is invoked, the Agent first does validation as specified in [Section 4.1.2](https://www.ietf.org/archive/id/draft-ietf-teep-protocol-10.html#vali…
-
I think what we're after for CoSWID+COSE is almost exactly the same as CWT+UCCS. It's not exactly the same because UCCS uses a different tag number than CWT and CoSWID doesn't.
I think we want to a…
-
The COSE spec mandates that the TBS (ie. the Sig_structure) be canonically encoded, eg. all the lengths must be encoded as short as possible. For example, a 3-byte protected header `{ alg: ES256 }`, w…
-
Using keys with a passphrase seems to lead to invalid signatures. To be reproduced and investigated.
-
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…
-
Hi letmaik:
Thank you and all other contributors for your work on this project. Hope you don't mind if me provide some suggestions.
In my understanding, the payload in this project is defined as a s…
-
## Null/Nil payloads
According to CIP-8, the payload in a COSE_Sign1 signature can also be null / nil, if the payload/message is known by both entities (sender/receiver). https://github.com/cardano…
-
### Update
I made 3 related proposals to the list:
- https://lists.w3.org/Archives/Public/public-vc-wg/2022Dec/0032.html
- https://lists.w3.org/Archives/Public/public-vc-wg/2022Dec/0011.html
…
-
When I run the original full CDDL of TEEP protocol in CBOR Diagnostic tool which is recommend by the CDDL RFC8610 Appendix F, the following is the error message.
![image](https://user-images.githubu…
-
https://microsoft.github.io/CCF/main/governance/hsm_keys.html
Need:
- [ ] CLI tool with same interface as `ccf_cose_sign1`, minus private key, to produce pre-hashed TBS
- [ ] CLI tool with same…