[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <003701ce41f9$74d8caf0$5e8a60d0$@net>
Date: Thu, 25 Apr 2013 16:11:29 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: Bleeding-jumbo branch updated from core
I will also have to add new test cases for JtR-ts. The md5 of the .inc
file itself is checked within the test suite, and it will ONLY run, if the
exact same .inc file is present.
Now, we can make 'new' test lines, once we have 'official' .inc files.
The reason for this, is I just grab 'some' words from within the inc run,
1500 of the first few (first couple 100 million, I think IIRC). But if
words were not generated in same order, then the run could be very long
indeed. Thus, the hash of the inc file is used, and if the same inc file is
not present, the TS simply will not test those incremental cases. It will
silently skip them, just like it does when a format is not build into the
JtR process.
Jim.
From: magnum Sent: Thursday, April 25, 2013 15:46
>
>I have merged latest commits from core CVS into the bleeding git branch. I
think it ended up right but there *may* be merge bugs.
>
>Worse, the bleeding branch now does not contain any working charset files
for Incremental, because the old ones are incompatible (at least for now).
Try creating new ones from the Rockyou list, for testing stuff.
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.
