[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP33074CAB1199CD90E97EAC9FDEC0@phx.gbl>
Date: Sun, 8 Jul 2012 08:13:04 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Inconsistencies in dynamic format names
This can be seen in the output of --subformat=list as well as in the
output of --test:
dynamic_0: md5($p) (raw-md5)
dynamic_1: md5($p.$s) (joomla)
dynamic_34: md5(md4($p))
dynamic_1001 md5(md5(md5(md5($p))))
dynamic_1002 md5(md5(md5(md5(md5($p)))))
dynamic_1010 dynamic_1010: RAdmin v2.x MD5
For dynamic_1010, dynamic.conf needs to be changed.
Expression=RAdmin v2.x MD5
instead of
Expression=dynamic_1010: RAdmin v2.x MD5
Since this has just been added yesterday, I don't think I need to adjust
benchmark-unify.
So, there's a simple patch attached
The other "problem" is that the built-in format names are printed with a
colon, whereas the user-specified aren't.
Should this be unified? If yes, which way?
If this gets unified, the benchmark-unify script needs to be adjusted as
well, but that is trivial.
Frank
View attachment "0001-Fix-dynamic_1010-format-name.patch" of type "text/x-patch" (725 bytes)
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.
