Skip to content

Conversation

@lumag
Copy link
Contributor

@lumag lumag commented Sep 15, 2022

The Keypair trait might be useful for representing relationship between
DigestSigner and DigestVerifier, RandomizedSigner and
RandomizedVerifier, etc. in addition to just Signer/Verfifier pair.

Relax type boundaries for the Keypair and AsyncKeypair traits.

Fixes #1106

The AsyncKeypair trait might be useful for representing relationship
between DigestSigner and DigestVerifier, RandomizedSigner and
RandomizedVerifier, etc. in addition to just Signer/Verfifier pair.

Relax type boundaries for the AsyncKeypair trait.

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
The Keypair trait might be useful for representing relationship between
DigestSigner and DigestVerifier, RandomizedSigner and
RandomizedVerifier, etc. in addition to just Signer/Verfifier pair.

Relax type boundaries for the Keypair trait.

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
@tarcieri
Copy link
Member

tarcieri commented Sep 15, 2022

This is technically a breaking change, in that downstream consumers that can presently rely on Keypair::VerifyingKey to impl Verifier<S>.

However, given I just shipped the first impls of this trait yesterday and the day before, I think it's rather unlikely there are any current users of the trait in its current form and we can just yank the associated releases.

I also strongly agree there's a rather big upside to being able to use this trait regardless of what other traits a given signature key type impls.

@tarcieri tarcieri changed the title relax Keypair type boundaries (#1106) signature: relax Keypair type bounds (#1106) Sep 15, 2022
@tarcieri tarcieri changed the title signature: relax Keypair type bounds (#1106) signature: relax Keypair type bounds Sep 15, 2022
@tarcieri tarcieri merged commit c593aa1 into RustCrypto:master Sep 15, 2022
@tarcieri tarcieri mentioned this pull request Sep 15, 2022
tarcieri added a commit that referenced this pull request Sep 15, 2022
As of #1107 this trait is shaped the same as `Keypair`, so there's no
need for it to continue to exist.

It will be removed in the next breaking release.
tarcieri added a commit that referenced this pull request Sep 15, 2022
As of #1107 this trait is shaped the same as `Keypair`, so there's no
need for it to continue to exist.

It will be removed in the next breaking release.
tarcieri added a commit that referenced this pull request Sep 15, 2022
As of #1107 this trait is shaped the same as `Keypair`, so there's no
need for it to continue to exist.

It will be removed in the next breaking release.
@tarcieri tarcieri mentioned this pull request Sep 15, 2022
tarcieri added a commit to RustCrypto/signatures that referenced this pull request Sep 15, 2022
Following RustCrypto/traits#1107 this relaxes the trait bounds to the
minimum requirements.
tarcieri added a commit to RustCrypto/signatures that referenced this pull request Sep 15, 2022
Following RustCrypto/traits#1107 this relaxes the trait bounds to the
minimum requirements.
tarcieri added a commit to RustCrypto/signatures that referenced this pull request Sep 15, 2022
Following RustCrypto/traits#1107 this relaxes the trait bounds to the
minimum requirements.
@tarcieri tarcieri mentioned this pull request Oct 31, 2022
scv35 added a commit to scv35/Signature-algorithms that referenced this pull request Jul 4, 2025
Following RustCrypto/traits#1107 this relaxes the trait bounds to the
minimum requirements.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

signature: Keypair not usable for keys not implementing the Signer trait

2 participants