RustCrypto / RustCrypto/traits
signature: tracking issue for `rand_core` (RandomizedSigner) stabilization
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 755
- Forks
- 256
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 2
Description
The signature crate contains the RandomizedSigner trait which are presently gated under the rand-previewrand_core feature.
Its main purpose is to allow a CSPRNG to be provided at the time a signature is computed. This is useful with algorithms like ECDSA or RSASSA-PSS which require an RNG at signing time.
There are also lingering concerns that deterministic signature algorithms like Ed25519 or ECDSA when implemented deterministically RFC6979 are brittle in the presence of fault attacks and should supplement their deterministic operation with additional randomness/entropy, which a RandomizedSigner API would allow for.
The main blocker at present is a 1.0 release of the rand_core crate.
Of all of the traits in the .signature crate, this one is by far the most underexplored/experimented with. So far there are no crates which actually impl it
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the RandomizedSigner trait documentation and reviewing the rand_core 1.0 release dependency described in this issue. The issue is a tracking item rather than a scoped code change; it is complete when the stabilization concerns and dependency blocker have been resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100