signature crate: 1.0 stabilization proposal by tarcieri · Pull Request #32 · RustCrypto/signatures

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri · 2019-10-10T18:22:11Z

The motivation for 1.0 stabilization of the signature crate is the upcoming 1.0 release of ed25519-dalek. In order to promote Ed25519 interoperability, it would be great if ed25519-dalek could use the traits from this crate along with the ed25519::Signature type from the ed25519 crate. See the relevant issue:

dalek-cryptography/ed25519-dalek#80

To get there, I think we need to do a 1.0 release of this crate, as well as the ed25519 crate.

The main impediment towards doing so is the digest crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a SemVer
breaking change.

To allow agility around digest, and signatory_derive which depends on it, this commit places access to both under the digest-preview and derive-preview Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-10T18:26:43Z

@newpavlov on a semi-related issue, I'm wondering if we should move the signature crate over to https://github.com/RustCrypto/traits (especially before a 1.0 release)

tarcieri · 2019-10-10T18:42:58Z

 name = "signature"
 description = "Traits for cryptographic signature algorithms (e.g. ECDSA, Ed25519)"
-version = "0.3.0" # Also update html_root_url in lib.rs when bumping this
+version = "1.0.0-pre" # Also update html_root_url in lib.rs when bumping this


Note: if we do this, I'd like to do a series of prereleases (e.g. 1.0.0-pre.0, 1.0.0-pre.1) to work through issues encountered with ed25519-dalek, signatory, and potentially rsa as well /cc @roblabla

tarcieri · 2019-10-10T18:44:27Z

One thing I'd definitely like to do before a 1.0 release is improve the state of the documentation, both for consumers of the trait, and for crates that impl the provided traits. Per #25 there are a number of undocumented design decisions which need to be adequately described.

The motivation for 1.0 stabilization of the `signature` crate is the upcoming 1.0 release of `ed25519-dalek`. In order to promote Ed25519 interoperability, it would be great if `ed25519-dalek` could use the traits from this crate along with the `ed25519::Signature` type from the `ed25519` crate. To get there, I think we need to do a 1.0 release of this crate, as well as the `ed25519` crate. The main impediment towards doing so is the `digest` crate is presently stuck at v0.8. It would be nice to be able to continue upgrading it, especially to a 1.0 release, but that would otherwise be a semver breaking change. To allow agility around `digest`, and `signatory_derive` which depends on it, this commit places access to both under the `digest-preview` and `derive-preview` Cargo features respectively, and calls them out as not covered under SemVer and subject to change, but breaking changes will be done with a minor version bump.

tarcieri · 2019-10-11T16:51:48Z

Going to move forward with an initial 1.0 prerelease using this plan. If anyone would like to get any changes in prior to a final 1.0, I don't plan on being too hasty in cutting that.

tarcieri · 2020-03-08T23:31:17Z

Note: final comment period for shipping signature 1.0 in ~2 weeks here: RustCrypto/traits#78

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

tarcieri mentioned this pull request Oct 10, 2019
Consider using traits/types from the 'signature' and 'ed25519' crates? dalek-cryptography/ed25519-dalek#80
Closed

tarcieri commented Oct 10, 2019
View reviewed changes

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 5332de2 to 26553c1Compare October 10, 2019 18:46

tarcieri force-pushed the signature-crate/1.0-stabilization-proposal branch from 26553c1 to b229861Compare October 11, 2019 16:34

tarcieri merged commit e1c8919 into masterOct 11, 2019

tarcieri deleted the signature-crate/1.0-stabilization-proposal branch October 11, 2019 16:52

tarcieri mentioned this pull request Oct 11, 2019
signature 1.0.0-pre.0 #34
Merged

newpavlov mentioned this pull request Nov 17, 2019
signature v1.0 #55
Closed

tarcieri mentioned this pull request Mar 8, 2020
signature: final comment period and intent to ship 1.0 RustCrypto/traits#78
Closed

Uh oh!

Conversation

tarcieri commented Oct 10, 2019• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tarcieri commented Oct 10, 2019

Uh oh!

tarcieriOct 10, 2019

Choose a reason for hiding this comment

Uh oh!

tarcieri commented Oct 10, 2019

Uh oh!

tarcieri commented Oct 11, 2019

Uh oh!

tarcieri commented Mar 8, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

tarcieri commented Oct 10, 2019• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tarcieri commented Oct 10, 2019

Uh oh!

tarcieriOct 10, 2019

Choose a reason for hiding this comment

Uh oh!

tarcieri commented Oct 10, 2019

Uh oh!

tarcieri commented Oct 11, 2019

Uh oh!

tarcieri commented Mar 8, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

tarcieri commented Oct 10, 2019• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tarcieri commented Oct 10, 2019

Uh oh!

tarcieriOct 10, 2019

Choose a reason for hiding this comment

Uh oh!

tarcieri commented Oct 10, 2019

Uh oh!

tarcieri commented Oct 11, 2019

Uh oh!

tarcieri commented Mar 8, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

tarcieri commented Oct 10, 2019• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tarcieri commented Oct 10, 2019

Uh oh!

tarcieriOct 10, 2019

tarcieri commented Oct 10, 2019•
edited
Loading

tarcieri commented Oct 10, 2019•
edited
Loading

tarcieri commented Oct 10, 2019•
edited
Loading

tarcieri commented Oct 10, 2019•
edited
Loading

tarcieri commented Oct 10, 2019•
edited
Loading