RustCrypto / RustCrypto/elliptic-curves
RustCrypto hardening recommendation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 874
- Forks
- 299
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 12
Description
It's recommended for the crypto libraries to integrate countermeasures against unexpected events, such as memory faults, arithmetic errors, and broken CPUs. In the event a computation is incorrect, detecting negative processes of this nature rather than releasing the outcome(s) of a faulty computation is preferable.
One can refer back to several publicly documented cases whereby a single faulty operation within the RSA PKCS signature scheme has leaked the private key. Deterministic ECDSA and EdDSA signature schemes feature similar properties.
Could RustCrypto crates contain sufficient self checks to detect faulty computations?
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
No files, tests, or entry points are named. Start by reviewing the elliptic-curve crates and the publicly documented faulty-computation cases referenced in the issue; the work is done only after a concrete self-check scope and validation approach are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100