[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6ipqO=TE5bravtMXiP6DpkM8tky1ROWqSk4N8znAYCjwCQ@mail.gmail.com>
Date: Tue, 10 Jul 2012 05:45:47 +0200
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: raw-sha256-cuda
2012/7/10 Solar Designer <solar@...nwall.com>:
> On Tue, Jul 10, 2012 at 05:29:11AM +0200, Lukas Odzioba wrote:
>> 2012/7/10 Solar Designer <solar@...nwall.com>:
>> > On Tue, Jul 10, 2012 at 05:11:15AM +0200, Lukas Odzioba wrote:
>> >> I limited PLAINTEXT_LENGTH to 19 chars so on TS now it is getting 1476/1500.
>> >
>> > Now that this passes TS, I guess we should remove the "unreliable" comment.
>> Should I send another patch for that?
>
> Please feel free to. I don't know what magnum prefers for trivial
> changes like this.
Attached patch same as above + removed unreliable comment.
>> Yes, I suppose that I should do something similar to myrice's code?
>
> In the long run, yes - but what myrice is doing will keep changing as we
> figure out how to do it best. So it is unimportant for you to do it
> now, and your time is in fact better spent on optimizing your slow
> hashes, etc. than on raw SHA-256 currently, now that you got it working
> to the same extent that other fast hashes on GPU do (at least passing
> test and reaching raw SHA-512's speed).
I agree.
Lukas
Download attachment "cudasha256speedpatch.diff" of type "application/octet-stream" (30380 bytes)
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.
