|
Message-ID: <000501d31d44$c0d20f90$42762eb0$@netscape.net> Date: Thu, 24 Aug 2017 21:52:04 -0400 From: <rs904c@...scape.net> To: <john-users@...ts.openwall.com> Subject: RE: Custom Windows build 1.8.0.9 - What happened to zip2john? You don't need cygwin to run the version I build because I include the appropriate DLL files. As long as you put the 13 DLLs (seperate zip file) in the run folder you should be fine running john.exe or john-omp.exe. The last time I compiled JtR, I was asked to put the DLLs in a separate .z file. -- Robert B. Harris from VA -----Original Message----- From: magnum [mailto:john.magnum@...hmail.com] Sent: Friday, August 18, 2017 12:44 PM To: john-users@...ts.openwall.com Subject: Re: [john-users] 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 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
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.