[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e61755d5a2c3993b69ee6105321a478f@smtp.hushmail.com>
Date: Tue, 03 Jul 2012 00:56:13 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: XSHA512 in Test Suite
On 2012-07-02 19:00, myrice wrote:
> On Mon, Jul 2, 2012 at 7:02 AM, magnum <john.magnum@...hmail.com> wrote:
>> Also, I noticed this:
>>
>> $ ../run/john --list=format-all-details | grep -A3 xsha512-cuda
>> Format label xsha512-cuda
>> Max. password length in bytes 125
>> Min. keys per crypt 524288
>> Max. keys per crypt 524288
>>
>> You only support a password length up to 16 characters, so why are you
>> announcing 125? I do not understand your use of MAX_PLAINTEXT_LENGTH in
>> the code.
>>
>
> No. In xsha512-cuda format(But not others). I support password length
> max to 125.
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?
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.
