ed25519-dalek
ed25519-dalek copied to clipboard
Fast and efficient ed25519 signing and verification in Rust.
Many users want a `verify_strict()` function which would reject signatures contain torsion components in the `R` portion of the signature, in the signer's corresponding public key, or in the product...
In batch verification, a random linear combination of the equations is taken. (I'm referring to the `P_i` in page 17 of the ed25519 paper, `P_i = 8*R_i + 8*H_i*A_i -...
`rand_core` is usually not compatible cross version, upgrading it here so it is usable with crates that use `rand >= 0.8`
Combines `verify_prehashed` and `verify_strict` to allow strict verification with prehashed values. Wrote an integration test (`repudiation_prehash`) however it fails intermittently as the `verify_prehashed()` call sometimes fails. I will need guidance...
The following code panics: ``` use ed25519_dalek::SigningKey; use ciborium; use rand; fn main() { let mut csprng = rand::rngs::OsRng; let key = ed25519_dalek::SigningKey::generate(&mut csprng); // JSON serde works let json_str...
I'd like to be able to sign/verify non-prehash signatures without the whole message in memory. The use case is for running on `no_std` embedded where the message is serialized directly...
When activating the `pkcs8` feature, the pkcs8/std flag is not activated thus `read_public_key_der_file` nor `read_public_key_pem_file` (when `pem` is activated) are available. I am new to rust and even more to...
My use case for it is as part of a round-trip test for serialising a SigningKey inside a program's config struct. I don't see any hazard adding this as a...
As requested [here](https://github.com/dalek-cryptography/ed25519-dalek/pull/196#issuecomment-1550194521), this PR contains my port of PR #196 to use the `hazmat` module instead of implementing any cryptographic *stuff* itself. I haven't copied over the added test...
This PR addresses issue #287. Tests pass with different combinations of features: "serde", "serde alloc", "serde std", "alloc".