Hyperledger Ursa (a shared cryptographic library) has moved to end-of-life status, with the components of Ursa still in use moved to their relevant Hyperledger projects (AnonCreds, Indy, Aries and Iroha).
I ask for this feature, because currently used version of k256 is pretty outdated and it loads some other oudated crates, which breaks my Iroha 2 build.
Specifically k256 depends on ecdsa which depends on signature. Given that dependency graph current ursa uses signature >=1.3.0, <1.4.0 and when I need to link with another crate which uses another version constraints for signature build fails because it fails to select a proper version. I.e.
I need to link my crate with ursa and with cargo crate. cargo v0.69.1 depends on more updated version of signature with signature >=1.6.2, <1.7 version constraint.
Looks like new version of k256 depends on the new version of ecdsa which depends on signature v2. With that it will be totally okay to have signature v1 and signature v2 in one crate.
I ask for this feature, because currently used version of
k256
is pretty outdated and it loads some other oudated crates, which breaks myIroha 2
build.Specifically
k256
depends onecdsa
which depends onsignature
. Given that dependency graph currentursa
usessignature >=1.3.0, <1.4.0
and when I need to link with another crate which uses another version constraints forsignature
build fails because it fails to select a proper version. I.e. I need to link my crate withursa
and withcargo crate
.cargo v0.69.1
depends on more updated version ofsignature
withsignature >=1.6.2, <1.7
version constraint.Looks like new version of
k256
depends on the new version ofecdsa
which depends onsignature v2
. With that it will be totally okay to havesignature v1
andsignature v2
in one crate.