Mitigation for poor documentation

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.

[LordDarkHelmet]

I am the author of that article. I am glad to help if needed.

If you (with volunteer friends or using a GitHub repository) create a set of tutorials, I'll add a link to them in all Stores (Snapcraft, Flathub [1] and GitHub releases) that I maintain.

Thinking out loud, they should contain:

• the main page:
  • how to download and install JtR (the basic stuff).
  • it is CLI and don't be afraid.
• plus links to some useful examples (e.g., cracking a zip file, Windows password, ...).
• if you have a mac, for example, off the top of my head, people would love to learn how to handle dmg files and "sparse bundles".

Of course, I'm just thinking out loud.

[1] FlatHub is more complicated, but the link will be in the manifesto.

[solardiz]

Thanks, @LordDarkHelmet! I think we should start by adding a link to your article to https://openwall.info/wiki/john/tutorials - can you please do that?

[LordDarkHelmet]

The link has been added.

[LordDarkHelmet]

@claudioandre-br I have added an additional link to an article I wrote for macOS / OSX
https://medium.com/@miningroi/cracking-tezos-ico-passwords-on-osx-6802253df1b9