[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP972E797684CCBE2AFADBBBFDFF0@phx.gbl>
Date: Tue, 19 Jun 2012 17:18:17 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: format renames
On 06/19/2012 03:55 PM, Solar Designer wrote:
> I think we can approach these more invasive renames separately, after
> next jumbo. Maybe along with JtR 1.8. Meanwhile, I don't mind starting
> to use "md5crypt" instead of "Crypt-MD5" and such in formats added in
> jumbo, so that we have fewer renames to make later.
May be we can support the old (legacy) names for a while without
actively advertising them, e.g., not mentioning them in usage output nor
supporting any bash completion, but allow interrupted sessions to be
restored.
We may even allow running new sessions using the old format names.
To make the transition easier, a warning message could be written to
stderr (and into the log file), pointing out the correct new name for
that format.
At least formats that have been part of official john releases or jumbo
releases should be treated that way.
(Formats introduced after john-1.7.9-jumbo-5 IMHO don't need that extra
effort.)
If john somehow provides a --list option for mapping old names to new
ones, even scripts such as relbench could make use of it.
Getting rid of all references to the old formats in the documentation,
tutorials, wiki, ... will take some time.
Finally removing support for the old names could be done some time later.
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.
