[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13c57b789985d5156f459a29333f1e07@smtp.hushmail.com>
Date: Fri, 18 Aug 2017 18:43:34 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Custom Windows build 1.8.0.9 - What happened to
zip2john?
On 2017-08-18 17:39, Glen B wrote:
> I was having issues with earlier builds and getting a hash of a ZIP file
> read properly (according to zip2john at the time, it was a pkzip2
> format). I've downloaded the latest Windows build from the wiki, John
> the Ripper v1.8.0.9-jumbo-1-bleeding (Bleeding version on 2017-03-06).
> Something that's new to me is that the zip2john executable seems to have
> been replaced with a different file. The text initially reads "symlink"
> with some non-text characters following. I'm assuming this is a linux
> symlink file, which neither Windows nor I know how to interpret.
>
> I'm not having much luck searching GitHub for an explanation of this
> change. Can anyone offer any tips on how I'm supposed to proceed with
> cracking a zip file at this point?
I believe you need to run from a Cygwin shell, not the CMD.EXE Windows
shell. If you can find a MinGW build instead I guess the problem will be
gone.
magnum
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.
