Date: Thu, 18 Aug 2011 19:47:42 -0500 From: "JFoug" <jfoug@....net> To: <john-dev@...ts.openwall.com> Subject: Re: pkzip format released. The inflateEnd/inflate/inflateInit2 are zlib stuff (libz) You may want ot make sure you are using the proper build for your icc. As for the x64, I will look into this later. Ignore the warnings. I will init them, but there are times when they are never accessed. The 'logic' is there, even though the compiler can not figure it out. Jim. ----- Original Message ----- From: "magnum" <rawsmooth@...dband.net> To: <john-dev@...ts.openwall.com> Sent: Thursday, August 18, 2011 7:19 PM Subject: Re: [john-dev] pkzip format released. > On 2011-08-19 00:22, jfoug wrote: >> It is up on the wiki (I also did another trivial patch). >> >> The pkzip format handles properly legacy encrypted files. Also modified >> zip2john process to build the hash. > > gcc warns about this: > > zip2john.c: In function ‘process_file’: > zip2john.c:262:33: warning: ‘best_off’ may be used uninitialized in this > function > zip2john.c:262:43: warning: ‘best_crc’ may be used uninitialized in this > function > zip2john.c:262:53: warning: ‘best_cmp_size’ may be used uninitialized in > this function > > Not sure if you get them or if they are of any importance, just wanted to > let you know. > > Also, it still fails self-test when built [linux-x86-64] with gcc: > get_hash(19). > > icc emits these cryptic warnings: > ipo: warning #11021: unresolved inflateEnd > Referenced in /tmp/ipo_iccjZeMHE.o > ipo: warning #11021: unresolved inflate > Referenced in /tmp/ipo_iccjZeMHE.o > ipo: warning #11021: unresolved inflateInit2_ > Referenced in /tmp/ipo_iccjZeMHE.o > > Not sure if that has anything to do with why gcc fails, but the icc build > works fine: > > I used the 2011-CrackMeIfYouCan_partX.zip files as real-world test. It > cracked them in 2 minutes, 6133K c/s :) > > 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.