Download John the Ripper Download Free – 1.9.0

John the Ripper is an open source password security audit and password recovery tool available for many operating systems.

What is John the Ripper?

John the Ripper is a password cracking tool originally produced for Unix-based systems. The main goal is to guess (“crack”) a password. It uses multiple modes to test password strength, such as dictionary, single crack, incremental and remote modes.

Is John the Ripper just command line?

Yes, John the Ripper is only a command-line program, on Windows as well as macOS and Unix-based operating systems.

Is John the Ripper free?

John the Ripper is free for personal use. There is also a Pro version designed for professional pen testers and ethical hackers.

How do I use John the Ripper?

For Windows users, download the zip file listed here. Extract the file and open the “run” folder using the command prompt. Once in the command prompt (you should see C:\john-1.9.0-jumbo-1-win64\run>), type “john” to run the program. Running C:\john-1.9.0-jumbo-1-win64\run>john will display all available options. Information for other operating systems you can check out the John the Ripper guides here.

Why is John the Ripper so popular?

Its immense popularity is due to its ability to detect password hash types automatically, run several types of attacks to include the classic dictionary attack as well as a brute force attack. In addition, it offers a free and open source version, as well as broad community support.

Characteristics

John the Ripper supports hundreds of hash and cipher types, including for:

• User passwords for Unix flavors (Linux, *BSD, Solaris, AIX, QNX, etc.)
• macOS, Windows, “web apps” (eg WordPress)
• Group item (e.g. Notes/Domino)
• Database servers (SQL, LDAP, etc.)
• Network traffic captures (Windows network authentication, WiFi WPA-PSK, etc.)
• Encrypted private keys (SSH, GnuPG, cryptocurrency wallets, etc.)
• File systems and disks (macOS .dmg files and “save bundles”, Windows BitLocker, etc.)
• Archive (ZIP, RAR, 7z)
• Document files (PDF, Microsoft Office, etc.)
• These are just some of the examples – there are many more.

What is new

These days, this original John the Ripper source tree serves primarily as the core tree for the John the Ripper jumbo. A 1.9.0 jumbo-1 release based on this 1.9.0 kernel is coming soon. Meanwhile, the bleeding jumbo branch on GitHub has already been updated to the 1.9.0 kernel.

Although this is a major release (after nearly 6 years since the 1.8.0 core release), the community’s progress in developing jumbo has been so much greater that any changes I make to the core are relatively minor, as is the core itself. Nevertheless, they are important. Besides serving as the core for jumbo, other uses of this tree include cases where core functionality alone is still sufficient or where (cross)compiling jumbo for a given target system is too difficult or (as a first step in) porting John the Ripper to an unusual new platform.

The following changes have been made between John 1.8.0 and 1.9.0:

• Increased the interleaving for bcrypt on x86-64 from 2x to 3x for a big speedup on non-SMT CPUs. Unfortunately, this sometimes results in a minor performance regression when running multiple threads on CPUs with SMT.
• Recognize the $2b$ bcrypt prefix.
• In the generic crypt(3) format, you detect decryption with valid vs. invalid salts as separate IDs for our heuristics on supported hash types.
• Introduced a number of optimizations for faster handling of large password hash files, including loading, cracking and “–show”. Some of these use more memory than before, but still in a more efficient way.
• Benchmark using all different candidate passwords with length 7 as default.
• Dropped undocumented special handling of “Mc” in “c” and “C” rule commands.
• Released undocumented limitation of the ‘M’ and ‘Q’ rule commands where they sometimes only remembered/checked up to the current hash-type’s length limit, but this optimization would not necessarily be transparent (eg if a later command would extract a substring from above the hash type’s length limit and bringing it to within the limit).
• Implemented special case handling of repeated rule commands ‘$’, ‘^’, ‘[‘, ‘]’, ‘{‘ and ‘}’, as well as faster handling of the ‘D’ command.
• When built with “–fork” support, disallow session names with integer suffixes as these conflict with those produced by “–fork”.
• Forward SIGTERM to –fork’ed children.
• Set stdout to the line buffer (rather than potentially the full buffer), except for “–stdout”, “–show” and helpers like “unshadow”.
• On Windows, restore normal handling of Ctrl-C in case our parent (like Johnny the GUI) had disabled it.
• Added linux-x86*-avx512 and linux-x86*-avx2 make targets, which use AVX-512 and AVX2 respectively for bitslice DES.
• Added linux-mic target for Intel MIC (first generation Xeon Phi, aka Knights Corner), which uses its 512-bit SIMD content for bitslice DES. (For second generation Xeon Phi, aka Knights Landing, use linux-x86-64-avx512.)
• Added linux-arm64le, linux-arm32le-neon and linux-arm32le make targets. (The first two of these use ASIMD or NEON for bitslice DES.)
• Added linux-sparc64 make target.
• Made a minor optimization to MMX and SSE2 assembly code for LM hash.
• Dropped Ultrix and SCO support.
• Don’t search for alternate configuration file names (like john.ini when on Unix).
• External mode example “DokuWiki” has been added to the default john.conf.
• Fixed operator precedence in the external mode compiler to be the same as C.
• Fixed an out-of-bounds typo in the virtual machine in remote mode.
• Fixed a bug introduced in version 1.7.4 in the dictionary rules engine, where some sequences of rule commands could overflow a word buffer.
• Fixed a bug where unaligned access SSE/AVX instructions were unnecessarily generated by GCC 4.6+ in the bitslice DES code in non-OpenMP builds.
• Fixed a bug where “Warning: no OpenMP support for this hash type” could be printed in “–stdout” mode.
• Made various other bug fixes, portability and documentation improvements.

Please stay tuned for the 1.9.0-jumbo-1 release and announcement, which will be “the real one”. There’s no way I’d be able to list the jumbo’s changes with the level of detail above – there have been far too many – but I plan to list the release’s highlights.