[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP166B698FBB4317E1741B6FDFDF00@phx.gbl>
Date: Sun, 10 Jun 2012 11:18:28 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Patch: allow --markov=SECTION in addition to --markov[=[MIN_LEVEL-]LEVEL[:START[:END[:[MIN_LENGHT-]LENGTH]]]]
On 06/10/2012 11:11 AM, magnum wrote:
> On 06/09/2012 09:18 PM, Frank Dittrich wrote:
>> As suggested the last time --markov=section has been discussed, I made
>> sure that the old behavior still works (and is the default when --markov
>> is used without specifying any values).
>>
>> --markov=SECTION is the only way to use several Markov sessions at the
>> same time which use different stats files - unless you use separate
>> config files.
>
> Sounds like an excellent patch but it needs some fixes:
>
> $ ../run/john --stdout --markov
> Segmentation fault
Oh, I don't know how I missed that.
(And I'll have to figure out what went wrong. But that shouldn't be too
hard.)
> $ ../run/john --stdout --markov=markov
> Statsfile not defined for Markov mode markov
>
> $ ../run/john --stdout --markov=markov2
> Statsfile not defined for Markov mode markov2
I thought about adding a more appropriate error message in this case.
But then I tested
$ ./john --incremental=doesnt_exist --stdout
No charset defined for mode: doesnt_exist
And then I thought, the first iteration doesn't need to be better than
the official john ;)
Frank
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.
