Single mode performance
Open
@magnumripper is already working on this.
Since Nov 22, 2018.
enhancement
RFC / discussion
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Single mode is one of JtR's most important features and AFAIK no other cracker has anything near it. But it's very relatively slow, mostly (or solely) due to rules processing. The fact GPU formats normally can't be used doesn't help, of course.
I intend to have a look-see & brainstorm for improvements. NOTE: The rules engine is a separate issue #3468.
- Perhaps some minor redesign could make it better suited for GPU?
- Audit / profile for bottlenecks. Jumbo may well have some bottleneck that John proper doesn't have.
- Perhaps optionally (opt-in) have word triples in addition to word pairs. This could dramatically increase the number of words produced. New rules commands needed would obviously include
3for referencing the third word, put possibly also some others: We have+now, for "the concatenation of both" but perhaps it's enough to just change that to "for concatenation of all". We also have a-preject flag "reject this rule unless word pair commands are currently allowed" so we'd add a-tflag for "reject this rule unless word triple commands are currently allowed" (note that this would also early-reject when word triples are not opted-in by some option).
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.
Assessment
This issue has not been assessed yet.