Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Jul 2015 04:21:43 +0300
From: Solar Designer <>
Subject: Re: Agnieszka's weekly report #10


On Tue, Jul 07, 2015 at 01:53:51AM +0200, Agnieszka Bielec wrote:
> Priorities:
> -yescrypt

I think your priorities should look more like this:

- Tune all PHC finalists implemented so far for the same defensive use
performance as is seen for bcrypt cost 5 for their most optimal
implementations on "well", and use the resulting cost settings for the
new test vectors (replacing those that were in there before):

- Re-do GPU benchmarks with those settings.  Possibly re-optimize.

- As necessary, revise the format name comments on all PHC finalist
formats implemented so far to correctly report the SIMD instruction set
in use, etc.

- Prepare some kind of report on the work so far, showing CPU vs. GPU
speeds for different cost settings and suitable for sharing it with the
PHC community.  [ You had this sort of data for your early POMELO code,
but that spreadsheet was too cryptic, referring to our system names
without giving hardware specs, etc. ]

- Integrate the existing yescrypt code into JtR.

- Switch all other PHC finalists implemented in JtR so far to use
yescrypt's *_region() functions for memory allocation (effectively
keeping it out of the loop):

- Implement yescrypt in OpenCL.  May take a look at the existing OpenCL
implementation being used for BSTY cryptocoin mining, and at Lyra2
authors' CUDA implementation.  (URLs were on the PHC discussions list.)

- Consider integrating Lyra2 authors' CUDA implementation of yescrypt as



Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.