Feature: print exact matching rule for a crack
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
during CMIYC, i realized it would give a huge productivity boost if there was a command-line option like --display-crack-rule which would show the exact rule that produced a crack.
example output:
bullshit1900 (TBu519) ('lAz"1900"<+')
this would allow to
- quickly share successful rules with team
- easily create new targetted ruleset based on only those that gave cracks
- learn rule syntax by example
i suspect in case of rules like korelogic after finding a number of matching rules this would give a speedup of > 1000x for future cracking.
in order to implement this every candidate would need to store an integer variable associating the candidate with the rule number/line.
Contributor guide
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 tracing the proposed --display-crack-rule option through the command-line handling and candidate processing, focusing on how a candidate could retain its rule number or line. Done means a cracked candidate can print the exact rule that produced it in the requested output style, without losing that association across the supported cracking paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100