[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6ba3c93dd605d92d9b4f2e1d10cb106@smtp.hushmail.com>
Date: Wed, 08 Feb 2012 10:22:59 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Recent github patches
On 02/07/2012 09:33 AM, Samuele Giovanni Tonon wrote:
> - i added mysql-sha1, which is basically sha(sha(p)) ,
> on my test i saw it going faster than on cpu. any test
> is really appreciated
Maybe you worked this out already, but here's the general way you add an
opencl format (that already exist as non-opencl) to the test suite:
1. Look at the non-opencl test line:
$ cd ../test
$ grep -i mysql-sha1 jtrts.dat
(base),(X),(jumbo),10000,MySqlSHA1,pw,mysqlSHA1_tst.in,mysql-sha1,N,X,(1500),(1500)
2. Add a similar line:
$ echo
'(opencl),(X),(jumbo),10000,mysql-sha1-opencl,pw,mysqlSHA1_tst.in,mysql-sha1-opencl,Y,X,(1500),(1500)'
>> jtrts.dat
Do not miss the 'N' that turns into a 'Y' (this controls whether TS
gives --format=xx to John or tries auto-detection, currently always 'Y'
for opencl - otherwise the CPU format may run instead).
3. Done! Now you can run "./jtrts.pl mysql-sha1-opencl" for testing just
this format, and it will be included when you test all of them using
"./jtrts.pl opencl".
> nsldaps, raw-md5, mysql-sha1 raw-sha1 now all support password
> up to 31 lenght.
This means their jtrts.dat lines should now end in ,(1500),(1500) for
including all supplied tests.
magnum
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.
