Date: Thu, 15 Oct 2015 12:52:17 +0300 From: Solar Designer <solar@...nwall.com> To: john-dev@...ts.openwall.com Subject: Re: PHC: yescrypt on GPU Hi Agnieszka, On Thu, Oct 15, 2015 at 12:48:23AM +0200, Agnieszka Bielec wrote: > 2015-10-06 2:16 GMT+02:00 Solar Designer <solar@...nwall.com>: > > So having better results, for better optimized code, would be helpful > > right now. And you'll need to revise it to include the 12 KB version, > > instead of the current 8 KB. I may provide it to you soon if you're > > ready to work on this. Please let me know. > > hi, it's still actual? Partially. I have since made the determination on which approach to go with ("the 12 KB version" and not a version with separate targeting of L2 cache). However, you will in fact need to update jumbo's yescrypt support to use that version. > I'm sorry, lately I was spending almost all my free time to preparing > for CTF's but now I see that I should change how I am spending my free > time, now I will be working on jtr harder > but what have the highest priority now? > still I have a bug in lyra2 ( and "FAILED (split() is only casing > sometimes (#4))" after "git pull upstream bleeding-jumbo") > I just read this email now I guess reading emails should be a higher priority. ;-) Other than that, for PHC you could update your JtR code to latest Argon2, which changed quite a bit since what you integrated. I think there are 3 flavors of it now, including a new flavor with a MAXFORM chain that I had proposed. You could also proceed to optimize it further - avoid register spilling, try splitting the 8 parallel BLAKE2b's across multiple work-items (combining their results via local memory, with a barrier). Did you see the thread on the PHC list about yescrypt on GPU? It's a similar approach I am suggesting here for Argon2. As to yescrypt, I intend to provide a new version to you in a week from now or so. Thanks, Alexander
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.