[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+YNibfb=W5MF==pcgawtYB_oFUcPg+9Kmz_NsxDKkhAHKjNqw@mail.gmail.com>
Date: Mon, 25 Jun 2012 08:42:28 -0400
From: cc <cc@...heads.com>
To: john-users@...ts.openwall.com
Subject: Re: Incremental Recovery format
Yes thanks for the references. It looks like Tavis solved the
problem which I encountered about work unit generation taking too
long. The only problem is that he'd need a long long in the External
mode (int won't cut it) unless he makes the stop point based on
length/fixed/count/numbers[] ... but it should be possible to patch
it into JtR directly.
The patch 'zuul' below allows you to use a '--stop' option to JtR
which will look for information in john.rec as to where to stop. The
focus of those two patches was on correctness (e.g. using --stdout one
can verify that 4 runs of All4 segmented is the same as All4).
https://github.com/ccdes/brutus/tree/master/jtr_patches
On Mon, Jun 25, 2012 at 8:33 AM, Camille Mougey <commial@...il.com> wrote:
> 2012/6/25 Rich Rumble <richrumble@...il.com>
>
>> On Mon, Jun 25, 2012 at 4:45 AM, Camille Mougey <commial@...il.com> wrote:
>> > Can someone give me a hint on the way rec_entry evolves ? Its relation
>> with
>> > the charset ?
>> > More generally, how can I cut the incremental pass in a lot of subtask ?
>> Seems like a popular idea:
>> http://www.openwall.com/lists/john-users/2011/06/29/2 (the entire
>> thread might be useful) and more recently:
>> http://www.openwall.com/lists/john-users/2012/06/05/16 and some work
>> done by Tavis: http://www.openwall.com/lists/john-dev/2012/06/14/5
>> Perhaps a search in the wiki or previous mail threads have some
>> answers, but I bet the source code has the "real" answers are in the
>> source.
>> -rich
>>
>
> Really interesting links, I didn't find them before. Great thanks, I think
> they'll be helpful :)
> Camille
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.
