[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 22 Mar 2012 21:30:19 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Self test woes
Solar (and all),
I think we have to to adjust/add/do something with the self-tests for
certain formats.
My OpenCL RAR format runs for very long per crypt_all() call: One call
can take half a minute or much more (though I'm hoping to do better).
The upshot is that it may contain thousands of candidates, or hundreds
of thousands, or more.
But the self-tests just tries one hash, crypts, tries another one, calls
crypt, etc. which make the self-test take forever (since one hash takes
just as long to do as half a million of them). I had to comment out the
fmt_self_test(format) call from benchmark_format() (but left the
benchmark in place) just to be able to work on my format.
I do not have any particular proposition though. Any ideas? This format
is extreme but I think the problem is noticable with most other GPU
formats too. Just disabling self-test with a flag would be easy but
that's not a good solution - we need the tests. Maybe we could have a
flag that tells john to collate all tests into just one or two calls to
crypt_all()?
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.
