john-users - RE: Speed of jtr on your machine?

Openwall wordlists collection for password cracking (20+ languages)

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 13 Sep 2011 11:50:50 -0500
From: "jfoug" <jfoug@....net>
To: <john-users@...ts.openwall.com>
Subject: RE: Speed of jtr on your machine?

>From: jfoug [mailto:jfoug@....net]
>
>>From: Solar Designer [mailto:solar@...nwall.com]
>>
>>On Tue, Sep 13, 2011 at 10:16:48AM -0500, jfoug wrote:
>>> Shouldn't linux-x86-64 build with sse-intrinsic code?
>>
>>Yes, but with gcc 4.4+ only.  I guess Bugtrace's older version of
>Ubuntu
>>has a pre-4.4 version of gcc.
>>
>>That said, my build of 1.7.8-jumbo-5 for linux-x86-64 with gcc 4.5.0
>>also prints "Raw MD5 [gen]", on E5420 2.5 GHz:
>
>Then I should look at that.  It 'should' give some signature that lists
>it
>was built using sse2 intrinsic functions.

Here is what I see in a 32 bit intrinsic build (cygwin). Now, this is not
jumbo-5, but I did not think anything changed about how md5_gen is built,
since then.

$ ../run/john -test -form=md5-gen
Benchmarking:  md5_gen(0): md5($p)  (raw-md5)  [SSE2 16x4x2 (intr)]... DONE
Raw:    9653K c/s

Benchmarking:  md5_gen(1): md5($p.$s)  (joomla)  [SSE2 16x4x2 (intr)]...
DONE
Many salts:     8321K c/s
Only one salt:  5404K c/s

Benchmarking:  md5_gen(2): md5(md5($p))  (e107)  [SSE2 16x4x2 (intr)]...
DONE
Raw:    5404K c/s

Benchmarking:  md5_gen(3): md5(md5(md5($p)))  [SSE2 16x4x2 (intr)]... DONE
Raw:    3788K c/s

Benchmarking:  md5_gen(4): md5($s.$p)  (OSC)  [SSE2 16x4x2 (intr)]...
Wait...
Session aborted



I will later check this on my pen drive linux-64 system, to see if there are
problems showing up there, which do not appear on this 32 bit build.

Jim.