Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E970E74.8000808@hushmail.com>
Date: Thu, 13 Oct 2011 18:14:44 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: how to print our the number of guesses john the
 ripper makes to crack a password

On 2011-10-12 22:58, Matt Weir wrote:
>     I just wanted to say that's a huge help for me. Previously I have
> been running cracking sessions twice, once to actually crack the
> hashes and a second time where I outputed guesses from JtR via stdout
> to a script I wrote that would record the number of guesses it took to
> crack the previously cracked passwords. To say that was hackish and a
> non-optimal solution to gather metrics would be an understatement ;)

Great! Personally I would prefer having it show how many password
candidates it has processed instead of this candidate*hash figure but
I'm not sure how to produce that number.

BTW, another thing I've been contemplating for lab studies is a command
line option for pegging keys_per_crypt to 1 regardless of what the
format says. This would make for a 1:1 correlation between rule and
guess in the log file, for studying which rules are most effective. But
I'm not sure how a format having min_keys_per_crypt > 1 would behave. Of
course, min_keys too would be forced down to 1 - but if the format was
not made for this I'm not sure if there could be problems (other than
the obvious performance drop).

magnum

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.