[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ea1cf84775a2cbdf6a3f625cba35e4d@smtp.hushmail.com>
Date: Sun, 10 Jun 2012 11:39:12 +0200
From: magnum <john.magnum@...hmail.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:35 AM, magnum wrote:
> On 06/10/2012 11:18 AM, Frank Dittrich wrote:
>> On 06/10/2012 11:11 AM, magnum wrote:
>>> $ ../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 ;)
>
> But the first case, --markov=markov should use the existing section
> [Options:Markov] so it should be the same as just saying --markov with
> no parameters. And it does have a statfile defined.
My bad. The default is [Options:Markov] but new ones are like
[Markov:name]. Seems to work fine (and I did not get the segfault when
using a custom section).
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.
