[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d883c2390ae6471b1f900b8b1d81ab1e@smtp.hushmail.com>
Date: Tue, 23 Jul 2013 11:41:22 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: PBKDF2-HMAC-SHA256
On 23 Jul, 2013, at 3:59 , magnum <john.magnum@...hmail.com> wrote:
> On 22 Jul, 2013, at 21:53 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
>> On 07/22/13 at 08:36pm, Lukas Odzioba wrote:
>>> 2013/7/16 Lukas Odzioba <lukas.odzioba@...il.com>:
>>>> Benchmarking: PBKDF2-HMAC-SHA256, rounds=12000 [PBKDF2-SHA256]... (4xOMP) DONE
>>>> Raw: 704 c/s real, 176 c/s virtual
>>>
>>> Attached OpenCL version.
>>
>> Committed "pbkdf2-hmac-sha256-opencl.diff" to bleeding-jumbo.
>>
>> There is *no* need to use the "any_cracked" approach in this format. Let
>> us try not to repeat my past "sins" ;)
>
> Right. This is better, although it doesn't affect speed for a slow format like this
As I had the code edited and tested, I committed it now just for good measure.
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.
