[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <caeee8181a5f708056e8c0c591468969@smtp.hushmail.com>
Date: Mon, 3 Jun 2013 02:50:14 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: bleeding-jumbo: raw-sha1-opencl uses fmt_default_split, other implementations use split() that unifies case.
On 3 Jun, 2013, at 0:41 , magnum <john.magnum@...hmail.com> wrote:
> On 2 Jun, 2013, at 23:35 , Frank Dittrich <frank_dittrich@...mail.com> wrote:
>> I just checked bleeding-jumbo, didn't check unstable.
>>
>> The other 3 implementations set the "The split() method unifies case" flag.
>>
>> raw-sha1
>> aw-sha1-ng
>> raw-sha1-linkedin (actually a different format)
>
> It also does not add any format tag, so .pot entries will be incompatible between CPU and GPU format. Which reminds me I really hate the fact we have to use dynamic tags for non-dynamic formats. It's very backwards. But until that is fixed, we need to use $dynamic_26$.
I have fixed the OpenCL format. I also made use of "compressed buffer" for plaintexts for reducing transfer latency.
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.
