We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signer
SecretKey
This is the case for SigningKey in RustCrypto. But what dangerous scenarios does that really prevent?
SigningKey
For those not familiar with the concept in Rust: currently one can do this:
let sk = SecretKey::random(); let signer = Signer::new(&sk); // passed by reference, cloned inside // `sk` still usable here
A possible change matching SigningKey behavior is to do this:
let sk = SecretKey::random(); let signer = Signer::new(sk); // passed by value and consumed // `sk` cannot be used anymore
The text was updated successfully, but these errors were encountered:
clone()
Successfully merging a pull request may close this issue.
This is the case for
SigningKey
in RustCrypto. But what dangerous scenarios does that really prevent?For those not familiar with the concept in Rust: currently one can do this:
A possible change matching
SigningKey
behavior is to do this:The text was updated successfully, but these errors were encountered: