Thank you for highlighting the lack of expected c509 format description in the demo code! For simplicity, the code just expects the cbor content as a hex string. I added and pushed a small clarification + the example certificates from the draft (together with a bugfix).
If the updated code gives you errors, I would be happy if you wanted to share your certificate for investigation. Best Regards Joel Höglund On Mon, 29 Jul 2024 at 22:19, Sipos, Brian J. <[email protected]> wrote: > All, > > I’m looking into creating some example c509 certificates which make use of > SAN Other Name and EKU code points allocated by the current draft [1] for > BP security. I think I have a properly encoded c509 structure using native > signature, but don’t have a good way to verify that correctness. > > I tried using the tool under “c509_demo_impl” of the c509 source repo [2] > but just get errors when attempting to use it in the read-C509 mode with > “cargo r c …” and I’m not sure what I may be doing wrong (it’s not clear if > the input is supposed to be direct binary, which I have tried, or some > other form of text-encoding). Any help getting this tool, or some other > more appropriate tool, working would be appreciated. > > Brian S. > > > > [1] > https://www.ietf.org/archive/id/draft-ietf-cose-cbor-encoded-cert-11.html > > [2] https://github.com/cose-wg/CBOR-certificates > > > _______________________________________________ > COSE mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
