RustCrypto / RustCrypto/traits
`signature` v4 tracking issue
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 755
- Forks
- 256
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 2
Description
This is a tracking ticket for potential breaking changes in a hypothetical signature v4 which didn't make it into the signature v3 release:
- #2168: this is a potential alternative to the
DigestSigner/DigestVerifierAPIs which avoids the limitations of using a callback. It's not quite as flexible in that it can't cover "streaming" Ed25519 signing/verification too, but that case it a bit more fraught. - #2393: this would be more flexible in terms of bounds
- #2394: this PR provided a cleaner approach to fallibility (at the cost of another combinatorial explosion in the number of traits), but our signature implementations weren't ready for it internally, and while it's probably a good change
signaturev3 had been dragging on too long
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
Review issues #2168 and #2393, and the approach described in #2394, to understand the proposed breaking changes for signature v4. This tracking work is complete when each proposal has a clear disposition and the v4 scope is documented.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100