[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <002401cbe3e5$b7d2c2d0$27784870$@net>
Date: Wed, 16 Mar 2011 09:23:27 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: Changing --markov[=LEVEL[:START:END[:MAXLEN]]] to --markov[=SECTION]
>-----Original Message-----
>From: Simon [mailto:simon@...quise.net]
>On 16/03/2011 07:37, Frank Dittrich wrote:
>> That means, instead of specifying all the options on the command line
>> [snip]
>
>I almost only use markov through load balancing scripts, hence the
>current interface. Using distinct stats files is however a good idea. I
>am using distinct john.conf files to achieve this effect ...
Since markov is a jumbo addition, then worrying about john changing versions
to 1.7.7 should not impact its direction of development.
I see pro's and cons for both methods. I actually think allowing multiple
john.conf subsections for different markov setups is a good idea. However,
as is, nothing beats simply typing new params on the command line.
I think if ALL markov params were command line syntax switches, or all
params were in a single john.conf section, then things would be better. As
we have it today, we have some params on the command line, and some set
globally in john.conf. Thus, as Frank is posting with his query, it is not
ideal.
Jim.
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.
