Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <55F9C5D6.5020806@openwall.net>
Date: Wed, 16 Sep 2015 14:41:10 -0500
From: jfoug <jfoug@...nwall.net>
To: john-dev@...ts.openwall.com
Subject: Re: fast hash processing bottlenecks


On 9/16/2015 2:31 PM, Solar Designer wrote:

> A "rules first" mode would help greatly (apply each rule to current
> word, then advance to next word; right now, we do it the other way
> around, which works better for probability-optimized rulesets and slow
> hashes).
I would really like a mode like that (especially the ability to choose 
between depth or breadth first from command line)

> The potential speed for the current raw-md5 code on this machine is:
>
> Benchmarking: Raw-MD5 [MD5 128/128 SSE4.1 4x3]... DONE
> Raw:    21811K c/s real, 21811K c/s virtual
>
> per core.  But we don't reach anywhere near it with wordlist mode.
> We do reach 21M+ per core with --fork=8 e.g. in mask mode.  20M for
> incremental mode locked to length 8.  Also, 19.7M for wordlist+mask
> (tested with -mask='?w?a?a').  But not for wordlist+rules.
>
Rules are pretty slow (when dealing with fast hashes).  that is why I 
was very happy when mask came out, and was damn near the speed of the 
format, while still allowing some good mangling (at least prepend/append 
which catches a damn lot of RW cracks).  Is it much worse for jumbo than 
for john-proper ?

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.