[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20120714003435.D5NI4.556307.imail@eastrmwml107>
Date: Sat, 14 Jul 2012 0:34:35 -0400
From: <jfoug@....net>
To: john-users@...ts.openwall.com
Subject: Several new crypt types added to JtR dynamic format
These changes have only been made to the git repository, magnum-git. The source tree for this version can be pulled by doing:
git clone git://github.com/magnumripper/magnum-jumbo directory
Directory can be changed to any name you like, such as magnum-jumbo. The source tree will be in a normal JtR source layout.
Here are the changes.
1. there is a 'native' sha2.c file (generic sha224, sha256, sha384 and sha512), in JtR source. So if JtR is built with an older version of OpenSSL, this generic code will be used. So the JtR generic sha2 code eliminates this version dependency, and allows many formats which use sha2 crypts, to become 'plugin formats'
2. Added 5 new crypt types into dynamic. All sha2’s (224, 256, 384, 512), and GOST.
3. Added 3 built in dynamic formats for each crypt type: ($p) ($s.$p) and ($p.$s).
4. Each new crypt type has been ‘given’ a reserved 10 numbers, for other formats, as we add them. Sha224 gets 50-59, sha256 gets 60-69, etc. The numbers are arbitrary, and of our own making, but it would be nice to get ‘some’ semblance of grouping.
5. Added a new ‘thin’ dynamic format, formspring. This was added specifically for the next item.
6. Added a new regen-salt type (6). This is for formspring, and the salt is $s.$p where salt is 2 digits, and the hash is dynamic_61 sha256($s.$p).
7. The TS has been fully updated (for all new SHA2 and gost formats in dynamic). All new format have, been fully tested, and are working. The TS is also in git, and can be obtained by: git clone git://github.com/magnumripper/jtrTestSuite ./test
8. Pass_gen.pl (script that can build many crypt type hashes) has been fully updated for all new dynamic types, and can handle expressions just like the md5/sha1 expressions, but now for sha256, sha512, gost, etc. All the new formats. So now sha256(MD5($p.$s).gost_64($s.$p).$p) will output the proper sha256 string, after building the uppercase hex md5 of $p.$s appending the base-64 gost output of $s.$p, and appending $p to the tail end.
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.
