[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <F3F07E7A09754D1A8EB9310473081C3F@D9VGLK61>
Date: Sat, 7 May 2011 17:48:15 -0500
From: "JimF" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: Test suite
Right now, the test suite only tests wordlist for multiple formats (not all
of them, so there still is some work to get hash sets for the formats not
yet done).
The test suite should be enhanced to test for rules, and other things, such
as single, *.chr running, markov, etc.
so the things I can see needing work on the test suite are:
1. fill in the missing input files. This will require building some hash
building routine (I have the perl scripts, but I have used all formats that
I have done in them already). Once a method is build to generate the
scripts, then the proper passwords fromt he pw.dic file are fed into it, and
formatted so that the format type, and the password are on the line, which
makes it much easier to figure out problems, when there are passwords
missed.
2. it should be put into a 'standard' location, and done as a patch, or tar
(patch prefered).
3. Add testing for rules / single. In this, simply testing md5_gen should
be enough, right?
4. Add a 'test' rule to the make file (and put in the patch). We might add
a wget to the make test rule, so that if the test data is not there, we get
it ??? If we do that, then we do not have to disto the test script, but if
someone does a make test, it will work for them. Then if only 1 in 5 do
this, they will have it work for them, without doubling or tripling the size
of the install for the other 4/5 of the users.
5. Add any other testing stuff. This may be over my skill set, and others
may have a better idea on what/how to do this.
6. Possibly tie the test suite into the GUI (once it is done).
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.
