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
in crypto/provider/ring/signature.rs
impl crate::crypto::provider::Signature for SignatureScheme { fn sign(&self, sign_key: &[u8], message: &[u8]) -> Result<Bytes> {
SignatureScheme::ECDSA_P256_SHA256 and SignatureScheme::ECDSA_P384_SHA384 currently are using the following four RustCrypto crates for sign functions.
"signature", "ecdsa", "p256", "p384"
https://docs.rs/ring/latest/ring/signature/struct.EcdsaKeyPair.html doesn't provide from_seed_unchecked like Ed25519KeyPair (https://docs.rs/ring/latest/ring/signature/struct.Ed25519KeyPair.html).
The text was updated successfully, but these errors were encountered:
briansmith/ring#889 is still under review.
Sorry, something went wrong.
No branches or pull requests
in crypto/provider/ring/signature.rs
impl crate::crypto::provider::Signature for SignatureScheme { fn sign(&self, sign_key: &[u8], message: &[u8]) -> Result<Bytes> {
SignatureScheme::ECDSA_P256_SHA256 and SignatureScheme::ECDSA_P384_SHA384 currently are using the following four RustCrypto crates for sign functions.
"signature", "ecdsa", "p256", "p384"
https://docs.rs/ring/latest/ring/signature/struct.EcdsaKeyPair.html doesn't provide from_seed_unchecked like Ed25519KeyPair (https://docs.rs/ring/latest/ring/signature/struct.Ed25519KeyPair.html).
The text was updated successfully, but these errors were encountered: