Add crate for weak key testing using basic statistical criteria
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 674
- Forks
- 170
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 10
Description
We can start with chi-squared test and check that number of bits set to 1 falls into a certain range. The function should probably be generic over input sizes larger or equal to 64 bits.
See this comment for additional context.
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 issue description and the linked pull-request comment for the proposed weak-key testing context. Define the crate scope, chi-squared criteria, supported input sizes, and validation approach before choosing an implementation; the issue does not name files or tests, so completion criteria still need to be established.
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
- 25/100