Orie Steele

This is blocking the next minor release... and fixes to : - https://github.com/veraison/go-cose/issues/181

I recall based on our previous meeting, we said our policy should be: Release Policies - Folders for release polices - Minor releases are reviewed by maintainers - Major release...

https://datatracker.ietf.org/doc/html/rfc8152#section-8.2 Not sure if there are test vectors that we can import, but we should start by finding and linking them.

Blocked pending: https://github.com/gluecose/test-vectors/issues/15

Unblocked I think, see: https://github.com/gluecose/test-vectors/issues/15#issuecomment-1752432446

its still progressing, the code points have changed. its also debatable if this should be done in this repo, will there be a go-cwt ?

@thomas-fossati @qmuntal do you think we should do all the CWT stuff in a seperate repo? if so, this issue should probably be closed.

PR is up here: https://github.com/veraison/go-cose/pull/183

EcdsaKoblitzSignature2016 GraphSignature2012 LinkedDataSignature2015 LinkedDataSignature2016 privateKeyPem (all private members to be moved to a new context with -private postfix.)

Not sure regarding `Ed25519Signature2020`.... we could reserve it... we might also reserve https://github.com/decentralized-identity/SchnorrSecp256k1Signature2019 which nobody has implemented.