Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANnLRdhHXMPSVN6HuykqAATfXofRYk5xhT1eTj8qWaVYEyh2Ew@mail.gmail.com>
Date: Tue, 29 May 2012 15:09:14 -0600
From: Stephen John Smoogen <smooge@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: john.conf options subsections

On 29 May 2012 14:59, magnum <john.magnum@...hmail.com> wrote:
> In Jumbo, we currently have no subsections of Options in john.conf. In
> next Jumbo (magnum-jumbo git repo), we have [Options:OpenCL]. I'm
> contemplating the introduction of a couple new ones (suggested by Frank
> several times and I think someone else too wanted it):
>
> [Options:Markov]
> the Markov options will be placed here
>
> [Options:MPI]
> the MPI tweak options will be placed here
>
> [Options:Jumbo]
> all remaining Jumbo-only options will be placed here
>
> However, this will lead to problems if people try to use an outdated
> config with a new Jumbo build. But there will likely be problems anyway,
> as the dynamic format has changed a lot. I think any user upgrading will
> need (and want) to sync his config files anyway.
>
> Is this OK? Or would I have to make ugly kludges for loading from
> deprecated places? If the latter, I think I'll just forget about it and
> leave it flat.

Is there a way to detect if an option file is too old? That way you
can flag it right off and say "you need to update please sir."

> magnum
>



-- 
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me."  —James Stewart as Elwood P. Dowd

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.