Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 2 Aug 2019 15:28:39 +0200
From: Solar Designer <>
Subject: Re: Guide: Installing John the Ripper on Windows 10

Hi Matt,

On Thu, Aug 01, 2019 at 10:52:58PM -0400, Matt Weir wrote:
>     I recently installed John the Ripper (Bleeding-Jumbo), on a Windows 10
> laptop using the new Windows Subsystem for Linux (WSLv1) feature. It seems
> to work great and was a lot easier than previous methods I've tried so I
> ended up putting together a guide on what I did to help other people who
> may be interested. You can view it here:

Please add this to the top of the "External links (English)" list at:

We should also clean this page up from dead links (obvious) and outdated
content (not so obvious).

Besides installing in WSL or Cygwin, you could have installed our
1.9.0-jumbo-1 release Windows binaries, which are still not too old.
Should be easy.

There are also Claudio's semi-automated Windows builds available via the
"Download Windows Build" label from the top of here:

Currently it points to:

Maybe mention these alternatives in your blog post?

Regarding the benchmarks you ran, for actual cracking of Raw-MD5 and LM
you'd use "--fork=8".  This should be obvious for Raw-MD5 where we don't
enable OpenMP by default because if its poor OpenMP scaling, but for LM
the benchmark appears to use OpenMP as a side-effect of us using shared
DES code for hashes that do show decent OpenMP scaling and for LM, which
doesn't.  When you actually load LM hashes for cracking, you'd be warned
about that, and "--fork=8" would be suggested.  You could want to add a
note about this so that people don't think you're showing your system's
full performance at those hashes.



Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.