[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 4 Jun 2011 21:52:37 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: ETA for incremental
magnum -
In my testing, the ETAs are misleading:
$ ./john -i pw
Using phpass mode, by linking to md5_gen(17) functions
Loaded 7 password hashes with 7 different salts (PHPass MD5 [phpass-MD5 MMX])
guesses: 0 time: 0:00:00:01 0.00% (ETA >Sun Jun 5 00:15:43 2011) c/s: 289 trying: 1211 - mikki
guesses: 0 time: 0:00:00:05 0.00% (ETA >Sun Jun 5 11:29:07 2011) c/s: 323 trying: 48680309 - 48884636
guesses: 0 time: 0:00:00:15 0.00% (ETA >Mon Jun 6 15:32:36 2011) c/s: 332 trying: moopy - molfe
guesses: 0 time: 0:00:00:19 0.00% (ETA >Tue Jun 7 02:46:01 2011) c/s: 332 trying: shells - marren
guesses: 0 time: 0:00:00:37 0.00% (ETA >Thu Jun 9 05:16:18 2011) c/s: 340 trying: shilley - shilen1
guesses: 0 time: 0:00:01:35 0.00% (ETA >Thu Jun 16 00:00:37 2011) c/s: 347 trying: moreter - moodles
guesses: 0 time: 0:00:08:03 0.00% (ETA >Sun Jul 31 08:40:29 2011) c/s: 337 trying: shalo1 - shello
guesses: 0 time: 0:00:08:59 0.00% (ETA >Sat Aug 6 21:48:06 2011) c/s: 339 trying: asagar - bordit
guesses: 0 time: 0:00:09:52 0.00% (ETA >Sat Aug 13 02:30:38 2011) c/s: 339 trying: mathia - maggly
guesses: 0 time: 0:00:16:59 0.00% (ETA >Sun Oct 2 00:36:10 2011) c/s: 337 trying: allay - allys
At this speed, this session is supposed to terminate in about 4 million
years (if nothing gets cracked), which could probably be determined
after just a few seconds of running (once the c/s rate is known).
Rather than say that ETA is beyond some date in 2011, perhaps John
should detect this typical case and say "ETA: never" or something like
that? Also, where do the dates in 2011 come from? Some overflow bug?
Thanks,
Alexander
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.
