[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d74fb653546a8cdb34c98273eb7d18f0@smtp.hushmail.com>
Date: Wed, 18 Apr 2012 00:04:43 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Crowd-sourcing statistics and rules
On 04/17/2012 10:54 PM, Rich Rumble wrote:
> On Tue, Apr 17, 2012 at 1:48 PM, Frank Dittrich
> <frank_dittrich@...mail.com> wrote:
>> While useful, this information can be somewhat misleading.
>> The reason is that john is buffering passwords for performance reasons.
>> The buffer size depends on hash algorithm and compile options.
>>
>> That's why, the last rule mentioned prior to a "Cracked ..." line does
>> not necessarily indicate which rule really cracked this password.
>>
>> For larger word lists, the log file will in most cases report the
>> correct rule.
>> For very small word lists and for single mode, the reported rule will
>> more frequently be wrong.
> That is good to know, maybe it can be patched or an additional option
> added that gives a more "real time" log, I assume doing so has the
> potential to slow JtR down.
I already added a workaround for this issue long ago, it's there in
released Jumbo. The --mkpc=N option (note it's not shown in usage blob,
but in docs/OPTIONS) will force John to just do N (normally you'd use 1)
at a time, at the cost of performance.
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.
