Mitigation for poor documentation
Open
Nobody has claimed this yet.
documentation
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
As stated in https://www.openwall.com/lists/john-users/2019/06/05/3, we can "put screenshot/s of JtR in action in the main webpage". Maybe, we can link to good tutorials seen in the wild.
This is an example:
https://medium.com/@miningroi/cracking-tezos-ico-passwords-on-windows-10-43d8462adaec
- Updated;
- Screenshots;
- How to download and install JtR on Windows;
- Plus some examples of cracking.
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 reviewing the John the Ripper main webpage and the linked Openwall discussion and Medium tutorial. Determine where documentation screenshots or tutorial links belong; the work is done when the agreed additions are published on the main webpage, but this issue does not identify the page source or a precise scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100