[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00d301cd66b3$ee59bcd0$cb0d3670$@net>
Date: Fri, 20 Jul 2012 15:12:01 -0500
From: "jfoug" <jfoug@....net>
To: <john-users@...ts.openwall.com>
Subject: RE: Update to JtR Test Suite
There has been another update to the TS. These formats have been added:
django
dragonfly3-64
dragonfly4-64
formspring (thin-dyna_61)
EPI
episerver (v1 and v0)
hmailserver
nukedclan(nk)
radmin
rawsha0
SybaseASE
wbb3 (WoltLab Burning Board 3: sha1($s.sha1($s.sha1($p)))),
The new version of the TS is 1.12-11
>NOTE, the TS is targeted at JtR developers. However, it certainly can be
>used by end users, to make sure their build of JtR is working properly, and
>able to detect passwords. The TS is a large step past the internal
>'self-tests' within JtR.
>
>The test suite has been updated. It can be obtained from:
>
>git clone git://github.com/magnumripper/jtrTestSuite test
>
>Run the above command while in the 'root' JtR subdirectory, and it will
place
>the test suite into ./test, and then things like 'make test' will work
properly.
>
>This new version contains many new dynamic formats. Several of these new
>formats are ONLY available on the unstable and bleeding tree within the git
>repository.
>
>The new formats (note which ones are new, depends upon when you last
>retrieved the TS) can be seen in the JtrTestSuite.Manifest. The latest
>additions of formats are: dynamic_35,36,37,38 which are numerous salted
SHA1
>formats, the addition of SHA224, SHA256, SHA384, SHA512, GOST, WHIRLPOOL to
>the dynamic formats (3 formats for each time in the default release).
>XSHA512 added to GPU formats, sha256crypt and sha512crypt.
>
>Also added is checksums for running incremental mode JtR tests. The tests
>will ONLY run if the proper all.chr and or alnum.chr file are present.
>Proper here means that they are the same file used to create the input data
>file. If the input hash files, and the *.chr files do not match, this can
>easily make the TestSuite appear to lock up, when testing inc modes, IF the
>inc file does not produce the same stream of words. Also, if there is a
bug
>in the inc module, and it does not produce the correct results, then the TS
>will appear to lock up, when doing the incremental checks.
>
>One new requirement on the TS, is it now requires Digest::MD5 to be
>available. This module should be available in most Perl installs.
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.
