Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 18 Aug 2017 21:09:53 +0000
From: Glen B <>
To: "" <>
Subject: Re: Custom Windows build - What happened to

Ah, interesting! If you don't mind me changing the subject slightly, I'm 
really surprised by what came out of zip2john now. Originally when I ran 
it on my zip file, it would return a typical hash line. Now however, it 
creates a massive (~7.1MB) hash file from a ~1.7MB zip file, and john 
still says it can't read the hash. Here's the beginning of the output:


And it continues on with this massive hexadecimal string, where it 
eventually ends with this:

 > 89670717610473b4fd3510962114f86*$/pkzip2$:::::..\

I'm recognizing parts of this as a typical hash, but what's with this 
new massive hex string? Could this contribute to why john says it can't 
find a hash string out of this?


On 8/18/2017 12:55 PM, Solar Designer wrote:
> On Fri, Aug 18, 2017 at 07:16:03PM +0000, Glen B wrote:
>> I really liked the earlier versions of JtR that were self-contained and didn't require downloading anything else to be honest.
> This build wasn't meant to require anything extra either.  According to
> what you said, it's just a bug.
>> If this is just a symlink though, what is it symlink-ing to? The john binary? If so, couldn't I just run john directly?
> Yes.  You could run "john" directly if you copy or rename it so that
> it'd be called "zip2john".
> Alexander

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.