[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP14904FA1C655DDC22BD8556FDD90@phx.gbl>
Date: Thu, 19 Jul 2012 12:02:16 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: RFC: add more information to --list=build-info output?
The recent change of FMT_MAIN_VERSION from 9 to 10 in bleeding-jumbo
inspired me to look at what other information might be useful to see in
--list=build-info.
I came up with these:
Format interface version: FMT_MAIN_VERSION
Charset file version: CHARSET_V
Max. Markov mode level: MAX_MKV_LVL
Max. Markov mode password length: MAX_MKV_LEN
So, for 1.7.9-jumbo-6-fixes with the attached patch applied, the new
--list=build-info output looks like this:
Version: 1.7.9-jumbo-7RC
Build: linux-x86-sse2i
Arch: 32-bit LE
$JOHN is ./
Format interface version: 9
Rec file version: REC3
Charset file version: CHR2
CHARSET_MIN: 32 (0x20)
CHARSET_MAX: 126 (0x7e)
CHARSET_LENGTH: 8
Max. Markov mode level: 400
Max. Markov mode password length: 30
Compiler version: 4.6.3 20120306 (Red Hat 4.6.3-2)
gcc version: 4.6.3
What do you think?
Should I avoid adding information that is less likely to change (e.g.,
the Markov mode limits)?
Should I put Markov mode limits into one line, to save space for future
additions?
Is the charset file version useful at all? I just checked the contest
edition, and the version is still CHR2.
Is there other information which should have been added?
Frank
View attachment "0001-Add-FMT_MAIN_VERSION-CHARSET_V-and-MAX_MKV_-to-build.patch" of type "text/x-patch" (1182 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.
