Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGcw5iS11UbJdgw_3ZirHi1zinLgX4QzEexDzJp5JjBWTBstbQ@mail.gmail.com>
Date: Fri, 2 Aug 2019 06:26:32 +0200
From: Marc Brinkmann <marc.brinkmann@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Guide: Installing John the Ripper on Windows 10

Hey Matt,
Thank you for the guide :)
My thoughts about WSL2: It's supposed to be faster because it works
different.
In V1 Linux System Calls are translated by an API for the Windows Kernel.
In V2 a real Linux-Kernel runs on a Hypervisor, Hyper-V i guess ;)
https://devblogs.microsoft.com/commandline/announcing-wsl-2/


What makes it more complicated to get is the fact, that you need an Windows
Insider Build from the fast ring
Cheers
Marc

Am Fr., 2. Aug. 2019 um 04:53 Uhr schrieb Matt Weir <cweir@...edu>:

> Hi all,
>     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:
>
>
> https://reusablesec.blogspot.com/2019/08/installing-john-ripper-on-microsofts.html
>
>
> Note: This was done with Windows 10 Pro, build 1809.
>
> I've been told that the preview version of WSLv2 provides faster
> performance for applications, but installing WSLv2 requires significantly
> more effort so I don't know if I'll get around to trying that out. If
> anyone else has success with getting WSLv2 to run I'd be interested in
> hearing about it.
>
> Cheers,
> Matt
>

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.