|
Message-ID: <BN4PR11MB08826D526AA87C4DDF8F4218AA810@BN4PR11MB0882.namprd11.prod.outlook.com> Date: Sat, 19 Aug 2017 21:36:27 +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? 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*4d989f74b755ae9409f8da4da1fbb97cd3aa0cf5a9a9f07b7a92fd01d0c3223cab6253af1cbcf6322a6e22edf1bd082c03ed0b083fb35e853c36cff3c3ac355814 >>>> >>>> >>>> >>>> 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 >>> >> > >
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.