You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation is for P-256 and uses RDFC, but the standard changed its name to ecdsa-rdfc-2019, uses a new data integrity v2 context, and additionally allows P-384. We should allow backwards compatible usage of ecdsa-2019 but also add the new name and P-384 support. We should add JCS cryptosuite support as well or spin that off into its own library.
We could also deprecate this library and create an ecdsa-rdfc-2019 one that supports P-256 and P-384 and another ecdsa-jcs-2019 one -- and leave this library be. One way or another, we need to add the above capabilities.
The text was updated successfully, but these errors were encountered:
@BigBlueHat, yes, you can update it to point to ecdsa-rdfc-2019-cryptosuite but I'm not sure we have removed it from all active projects yet so we need to confirm that before archival.
The current implementation is for P-256 and uses RDFC, but the standard changed its name to
ecdsa-rdfc-2019
, uses a new data integrity v2 context, and additionally allows P-384. We should allow backwards compatible usage ofecdsa-2019
but also add the new name and P-384 support. We should add JCS cryptosuite support as well or spin that off into its own library.We could also deprecate this library and create an
ecdsa-rdfc-2019
one that supports P-256 and P-384 and anotherecdsa-jcs-2019
one -- and leave this library be. One way or another, we need to add the above capabilities.The text was updated successfully, but these errors were encountered: