[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <199b6b.dd4.1390661d1d3.Webtop.0@cox.net>
Date: Wed, 8 Aug 2012 09:17:17 -0400 (EDT)
From: jfoug@....net
To: john-dev@...ts.openwall.com
Subject: Re: Current -fixes GPU formats vs TS
The better way would be this:
(cuda)(gpu),(X),(jumbo)&(cuda),50,mscash2-cuda,pw,MSCash2_tst.in,mscash2-cuda,Y,X,(1500)(1410),(1500)(1410)
(...)
(opencl)(gpu),(X),(jumbo)&(opencl),50,mscash2-opencl,pw,MSCash2_tst.in,mscash2-opencl,Y,X,(1500)(1410),(1500)(1410)
This allows either 1410 or 1500 t be 'correct'. That way, if the format
is changed, and the salt length max is increased, then it will properly
detect the right amount. But it also accepts 1410 as correct, which is
what you get with 19 char salt max.
Jim.
On Mon, Aug 6, 2012 at 9:03 PM, Lukas Odzioba wrote:
> 2012/8/7 Lukas Odzioba <lukas.odzioba@...il.com>:
>> Why for mscash2-opencl expected count is 1410, while for mscash2-cuda
>> it is 1500 (both supports salts up to 19 chars)?
>>
>> form=mscash2-cuda guesses: 1410 time: 0:00:00:18 :
>> Expected count(s) (1500) [!!!FAILED!!!]
>> form=mscash2-opencl guesses: 1410 time: 0:00:00:26
>> [PASSED]
>
> OK Now I know.
> I found those lines in jtrts.dat:
>
> (cuda)(gpu),(X),(jumbo)&(cuda),50,mscash2-cuda,pw,MSCash2_tst.in,mscash2-cuda,Y,X,(1500),(1500)
> (...)
>
> (opencl)(gpu),(X),(jumbo)&(opencl),50,mscash2-opencl,pw,MSCash2_tst.in,mscash2-opencl,Y,X,(1410),(1410)
>
> Probably we should unify that.
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.
