Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 15 Dec 2012 12:40:26 -0200
From: Claudio André <>
Subject: Re: Benchmark versus incremental mode (speed)

Em 14-12-2012 23:55, Claudio André escreveu:
> Per definition, the real crack gives the real figure. If they differ
> it may be due to things like test vector length not matching the IRL
> run (in case the format suffers significantly from length) or if the
> IRL hash does not use 5000 iterations. If that's not it, I'm not sure.

It is test vector dependant (the patch below increases bench numbers). 
Since, i'm not sure how to produce a fair test vector, i won't do anything.

I attached a comparative "study" between bench and a real crack. 
Something like this:

../run/john -fo:format ~/file -inc --max-run-time=60

- The file contains only 1 (valid) hash.
- The hash was selected from one of the test vector from the CPU format 
file (if possible).
- JtR was not be able to crack it on 60 seconds.

Well, I always use the same test vector as the CPU format does. If 
anyone has a suggestion, please ping me.


  static struct fmt_tests tests[] = {
- {"$5$LKO/Ute40T3FNF95$fdgfoJEBoMajNxCv3Ru9LyQ0xZgv0OBMQoq80LQ/Qd.", 
+    {"$5$V8UMZ8/8.j$GGzeGHZy60318qdLiocMj7DddCnfr7jIcLMDIRy9Tr0", 
{"$5$kc7lRD1fpYg0g.IP$d7CMTcEqJyTXyeq8hTdu/jB/I6DGkoo62NXbHIR7S43", ""},
+ {"$5$EKt.VLXiPjwyv.xe$52wdOp9ixFXMsHDI1JcCw8KJ83IakDP6J7MIEV2OUk0", 
+ {"$5$LKO/Ute40T3FNF95$fdgfoJEBoMajNxCv3Ru9LyQ0xZgv0OBMQoq80LQ/Qd.", 

Compared results attached.

View attachment "results" of type "text/plain" (4455 bytes)

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.