[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <311faebd43f55bd9411b323ac95e7f3e@smtp.hushmail.com>
Date: Tue, 05 Jun 2012 08:24:59 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: GPU formats vs Test Suite
On 06/05/2012 08:07 AM, SAYANTAN DATTA wrote:
> On Tue, Jun 5, 2012 at 1:30 AM, magnum<john.magnum@...hmail.com> wrote:
>> These three do no seem to crack a single password IRL. The actual fault
>> *may* be in the TS but most of these passed the tests in February so I
>> think you should have a look at this. The easiest way to grab TS on bull is
>> from ~magnum/TestSuite_1.12-2.tar.bz2 - unpack it in your john
>> directory.
>>
> I found that the output of openssl version of pbkdf2 in mscash2(cpu
> version) do not matches with the SSE version of pbkdf2 for salts greater
> than 19 charachters. Since mscash2-opencl is based on openssl version of
> pbkdf2, so I have limited the max salt length to 19 charcters only. But the
> file /test/MSCash2_tst.in contains salts upto 22 character. I think this is
> the main source of problem.
How come not a single password is cracked then? A smashed buffer? It
should crack all passwords with <= 19 character salts.
This is what the TS is good at - we fixed loads of similar problems
right after Jim wrote the TS.
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.
