[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <005f01cc14f0$b6489b60$22d9d220$@net>
Date: Tue, 17 May 2011 20:15:36 -0400
From: "Robert Harris" <rs904c@...scape.net>
To: <john-dev@...ts.openwall.com>
Subject: RE: Jumbo-5-RC4 released (was: Jumbo-5 RC3 released (was...))
See the following on Solaris.
bash-3.00$ make clean solaris-x86-sse2-cc
make: Fatal error in reader: Makefile, line 37: Unexpected end of line seen
-----Original Message-----
From: magnum [mailto:rawsmooth@...dband.net]
Sent: Tuesday, May 17, 2011 5:35 PM
To: john-dev@...ts.openwall.com
Subject: [john-dev] Jumbo-5-RC4 released (was: Jumbo-5 RC3 released (was...))
On 2011-05-17 18:57, jfoug wrote:
> RC3 of jumbo-5 released. This RC3 has these changes:
>
> 1. fixed bug in NT format. It has to do with too much buffer being cleaned up after the password was added (unless the buffer was the 8x buffer in the 64 bit SSE builds). For 32 bit SSE/MMX or a nonSSE build, this gets about a 10% performance improvement as a side effect. The bug was showing up on 32 bit builds, where the tstall was listing 1190 or so passwords being found for NT (but only on 32 bit).
RC4 of jumbo-5 is released. This incorporates the same fix for the
"mscash" format that Jim found and fixed for NT.
It also pokes with a couple of #ifdef's so two previously MPI-only
features are enabled for normal builds too:
* Status progress and ETA for Incremental mode. After a stop-and-resume
this is muted as it's currently not stored in the .rec file. NOTE that
the ETA is muted (since Jumbo-5-RC1) if progress is 0.00% so for
"normal" incremental mode you will never see any ETA. But for
-inc:digits or -inc:alpha and fast formats, this come very handy.
* Force any size wordlist to memory, using --mem=0
I also added a few bits of more verbosity for self test failures, very
handy when debugging complex keybuffers like NT's.
enjoy!
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.
