Date: Wed, 25 May 2011 18:21:10 +0200 From: magnum <rawsmooth@...dband.net> To: john-dev@...ts.openwall.com Subject: Re: SSE bug still there in Jumbo-5-RC6++ Maybe the problem lies somewhere else and overwrites something in NSLDAP. I have traced the raw-MD4 segfault to be caused by raw-md5-unicode or MD5_go overwriting *out in raw_MD4's get_binary() before it is ever used. This makes it never get alloced... and it points to 0x67. Bang. If I disable raw-md5-unicode (by placing a "return 0" in valid()) the fault goes away. If I instead disable the "thatsworking" selftest (still in raw-md5-unicode) the fault goes away too. But that is just 12 characters out of max 53 so I'm not sure what is wrong. BTW if I revert the NSLDAP part of the latest SSE2 patch, NSLDAP is fine both in --test and all 1320 in testsuite, 32 or 64 bit. I also have problems with mssql on linux-x86-64 (test stuite only) magnum If I disable the raw-md5-unicode format ( On 2011-05-25 17:00, Erik Winkler wrote: > Jumbo-5-RC6++ works great on MacOS X for 64-bit build. No issues. > > On MacOS X using the sse2 build, I get the following error for NSLDAP benchmarking: > > Benchmarking: Netscape LDAP SHA SSE2 [SHA-1]... FAILED (get_hash(3)) > > Now this only occurs when running ./john -test. If I run ./john -test -format:nsldap, it works correctly: > > ../run/john -test -format:nsldap > Benchmarking: Netscape LDAP SHA SSE2 [SHA-1]... DONE > Raw: 7837K c/s real, 7837K c/s virtual > > Not sure why. > > Erik > > On May 24, 2011, at 1:58 PM, magnum wrote: > >> Even after applying all incremental patches posted to the wiki, there are some problems left in Jumbo-5-RC6: >> >> 1. Raw-MD4 segfaults for me on linux-x86-sse2: >> * Using linux-x86-mmx I saw no problem. >> * It segfaults when running "--test" >> * It does NOT segfault when running eg. "--test --fo:raw-MD4" >> * Test suit does NOT segfault and all 1320 is found >> >> This led me to believe the problem was in the format running right before raw-MD4 on a --test run, namely salted-sha1. I did find a bug in that format (fix included in patch just posted) but that was not the cause of this. >> >> 2. NSLDAP has a problem on linux-x86-sse2 and linux-x86-mmx: >> Benchmarking: Netscape LDAP SHA MMX [SHA-1]... FAILED (get_hash(1)) >> >> I have no time to investigate further right now. >> >> 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.