[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP77BC81E9AEB1279792B170FDF00@phx.gbl>
Date: Sun, 10 Jun 2012 11:31:36 +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:10 AM, Frank Dittrich wrote:
> Even if we commit the current patch as it is right now, the next step
> would just be another enhancement, not a change that is not compatible
> with any previous logic.
> (I'll have to check what currently happens with --markov=a:100 and a
> section [Markov:a:100] in john.conf.
> May be I have to add a check that the section name doesn't contain a
> colon. Currently this requirement is only mentioned in doc/MARKOV.)
Unfortunately, with a john.con section
[Markov:broken:100]
Statsfile = $JOHN/stats
MkvLvl = 200
MkvMaxLen = 12
$ ./john --markov=[tab][tab]
will list as possible completions:
$ ./john --markov=
broken:100 default
$ ./john --markov=broken:100 --stdout|head -n 3
MKV start (lvl=200 len=12 pwd=259356431)
chanererere
chanerereri
chanererera
So, if implementing the next enhancement tales longer, I should at least
make sure that section names containing colons are not supported.
Additionally, I'll have to fix the problem(s) found by magnum.
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.
