Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 07 Jun 2012 01:44:22 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: get_source() and bitmaps boost

I got the idea to use the 6.5 million leaked hashes for some speed & 
memory tests. All tests consist of running --incremental=digits to 
completion, with all those candidates already cracked (so crack prints 
does not slow things down).

Current magnum-jumbo:
$ ./john LinkedIn.raw-sha1_li -fo:raw-sha1_li --nolog -inc:digits
Loaded 6458020 password hashes with no different salts (Raw SHA-1-LI 
[SSE2i 8x])
Remaining 5583000 password hashes with no different salts
guesses: 0  time: 0:00:00:23 DONE (2012-06-07 00:58:35)  c/s: 26971G 
trying: 83536787 - 83536784

After applying the get_source patch (AND enabling get_source in 
rawSHA1_LinkedIn_fmt_plug.c):
$ ./john LinkedIn.raw-sha1_li -fo:raw-sha1_li --nolog -inc:digits
Loaded 6458020 password hashes with no different salts (Raw SHA-1-LI 
[SSE2i 8x])
Remaining 5583000 password hashes with no different salts
guesses: 0  time: 0:00:00:22 DONE (2012-06-07 01:04:52)  c/s: 28196G 
trying: 83536787 - 83536784

Current bleeding-jumbo (which includes get_source and also bitmaps):
$ ./john LinkedIn.raw-sha1_li -fo:raw-sha1_li --nolog -inc:digits
Loaded 6458020 password hashes with no different salts (Raw SHA-1-LI 
[SSE2i 8x])
Remaining 5583000 password hashes with no different salts
guesses: 0  time: 0:00:00:16 DONE (2012-06-07 00:57:56)  c/s: 38770G 
trying: 83536787 - 83536784

Bleeding-jumbo with the get_source stuff reverted:
$ ./john-bleeding-no-getsource test/LinkedIn.raw-sha1_li -fo:raw-sha1_li 
-pot:bleeding.pot --nolog -inc:digits
Loaded 6458020 password hashes with no different salts (Raw SHA-1-LI 
[SSE2i 8x])
Remaining 5583000 password hashes with no different salts
guesses: 0  time: 0:00:00:17 DONE (2012-06-07 01:36:54)  c/s: 36490G 
trying: 83536787 - 83536784


Memory usage (RSS peak):
magnum-jumbo: 875 MB
magnum-jumbo w/ get_source added: 530 MB
bleeding-jumbo: 674 MB
bleeding-jumbo w/ get_source reverted: 1 GB

Bleeding is 43% faster than magnum-jumbo because of these two changes, 
mostly because of the bitmaps. One way to put it is that the get_source 
patch regains all memory the bitmaps use, and much more. And it boosts 
bleeding-jumbo by another 6%.

magnum

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.