Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 20 Aug 2017 00:48:21 +0000
From: Glen B <lucky0106@....com>
To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com>
Subject: RE: Custom Windows build 1.8.0.9 - What happened to
 zip2john?

Iíve tried several older builds, including the official 1.7.9 and 1.8.0 jumbo builds. I believe some of the fixes I needed for working with ZIP files would only have made it to the 1.8.0.9 build unless someone can do a more updated windows build?

From: Rich Rumble<mailto:richrumble@...il.com>
Sent: Saturday, August 19, 2017 5:45 PM
To: john-users@...ts.openwall.com<mailto:john-users@...ts.openwall.com>
Subject: Re: [john-users] Custom Windows build 1.8.0.9 - What happened to zip2john?

On Sat, Aug 19, 2017 at 5:36 PM, Glen B <lucky0106@....com> wrote:

> It's been sitting as an email attachment since the beginning of the
> year, I wonder if it may have been corrupted at some point (although I
> did open it before, when I had the password). It has some of my medical
> records in it, I don't feel very confident about sharing it... Is there
> any other way I can help you?
>
>
> On 8/19/2017 10:42 AM, magnum wrote:
> > On 2017-08-19 17:22, Glen B wrote:
> >> I hope not... I just copied john to "zip2john" and ran it that way as
> >> Alexander suggested. Running john with no parameters outputs "John the
> >> Ripper 1.8.0.9-jumbo-1-bleeding MPI + OMP [cygwin 64-bit SSE4.1-ac]".
> >
> > Perhaps your zip file is thrashed some way. Any chance you can share
> > it with us (off-list if needed) so we can investigate?
> >
> > magnum
> >
> >>
> >> On 8/19/2017 2:44 AM, magnum wrote:
> >>> On 2017-08-18 23:09, Glen B wrote:
> >>>> still says it can't read the hash. Here's the beginning of the output:
> >>>>
> >>>>    >
> >>>> GBLabs.zip:$pkzip2$1*1*2*0*1c0f72*1ea40d*7830b902*0*29*8*
> 1c0f72*7830*7eee*4d989f74b755ae9409f8da4da1fbb9
> 7cd3aa0cf5a9a9f07b7a92fd01d0c3223cab6253af1cbcf6322a6e22edf1
> bd082c03ed0b083fb35e853c36cff3c3ac355814
> >>>>
> >>>>
> >>>>
> >>>> And it continues on with this massive hexadecimal string, where it
> >>>> eventually ends with this:
> >>>>
> >>>>    > 89670717610473b4fd3510962114f86*$/pkzip2$:::::..\GBLabs.zip
> >>>>
> >>>> 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?
> >>>
> >>> You weren't using an older version of John than of zip2john, were you?
> >>>
> >>> magnum
> >>>
> >>
> >
> >
>
> Don't forget too that there are community builds that would still have the
> behavior you're looking for (zip2john.exe)
> http://openwall.info/wiki/john/custom-builds the one from 2015 I think
> has the exe still but will lack any new fixes or updates
>


Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ