[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1e0c9c5f930ca56d88ee5be7ccfda9c0@smtp.hushmail.com>
Date: Tue, 03 Jul 2012 16:42:30 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: XSHA512 in Test Suite
On 2012-07-03 15:31, myrice wrote:
> On Tue, Jul 3, 2012 at 6:56 AM, magnum <john.magnum@...hmail.com> wrote:
>> In that case, the jtrts.dat entry for xsha512-cuda should end in
>> (1500),(1500) but if I try that, it fails.
>>
>> form=xsha512-cuda guesses: 1468 time: 0:00:00:13 :
>> Expected count(s) (1500) [!!!FAILED!!!]
>> .pot CHK:xsha512-cuda guesses: 1468 time: 0:00:00:13 [PASSED]
>>
>> ...and the 1468 cracked strongly suggests it really only cracks
>> passwords up to 16 characters.
>>
>> So should I commit this (1500),(1500) into Test Suite and you fix
>> whatever bug is in there?
>>
>
> Yes, I can debug this faster with TS. Please do that.
Done.
> BTW, how to use TS? I just run ../jtrTestSuite/jtrts.pl I have to
> wait for so long.
When testing GPU builds, always use -noprelims (otherwise it'll run a
--test=0 which takes ages). Use --help for other options.
> Can TS tests one format only? Besides, from output, I didn't see
> form=xsha512-cuda/opencl there.
I think the default is not testing any GPU formats. Try "./jtrts.pl
-showtypes" for all available types. A type can be one or more single
formats, like "xsha512-cuda" or a whole class, like "cuda" or "opencl"
(or "gpu" which does both"
> Here is what I get using ./john -fo=xsha512-cuda ../jtrTestSuite/XSHA512_tst.in
> guesses: 154 time: 0:01:51:26 0.00% (3) c/s: 65574K trying: fkus1f
> It only guesses 154 passwords. I don't get 1468.
> And I notice it consumes so much memory. > 50% of 8GB memory. It
> should not take so much memory.
for doing this manually, add -wo:../jtrTestSuite/pw.dic
Or just "cd ../../jtrTestSuite" and "./jtrts.dat -noprelims -stoponerror
xsha512-cuda".
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.
