[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120619135535.GB16936@openwall.com>
Date: Tue, 19 Jun 2012 17:55:35 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: format renames
On Tue, Jun 19, 2012 at 09:01:02AM +0200, magnum wrote:
> Done. I also patched a number of Lukas' formats that you missed due to
> even stranger use of the macros (they had other names for ALGORITHM_NAME).
Oh. What specific formats?
> I left the GPU format names as Crypt-MD5 although it's not consistent
> with FreeBSD MD5. Not sure what to do, maybe the latter should be
> changed even though it's more clear in our eyes.
You're right. I am not too happy about either name for this one.
Here's an attempt to standardize crypto algorithm names:
http://www.users.zetnet.co.uk/hopwood/crypto/scan/
and specifically:
http://www.users.zetnet.co.uk/hopwood/crypto/scan/ph.html
but these are not de-facto standard names either (some are, some are not).
Since phk (the author) refers to his creation as md5crypt, maybe we
should use that name. Then also bcrypt and I guess descrypt. And then
we could also want to rename the format labels accordingly, which will
unfortunately break existing/old tutorials/scripts.
In 1990s, no one cared about cracking raw MD5 hashes, so simple format
labels like DES and MD5 made sense, referring to the crypt(3) flavors,
which was all that mattered. Now having MD5 as the format label is
confusing - some people would expect it to mean MD5 itself (raw), not
md5crypt.
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.
Alexander
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.
