Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 19 Aug 2015 05:18:47 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: PHC: Argon2 on GPU

Agnieszka,

Am I correct that all of your work on Argon2 so far is on revision 1.0,
without BlaMka and without the indexing function enhancement?  (I hope
you're keeping track of relevant discussions on the PHC list.)

In other words, where and when did you obtain the Argon2 code that you
integrated and ported to OpenCL?  What revision numbers did it have on it?

On Wed, Aug 19, 2015 at 04:10:18AM +0200, Agnieszka Bielec wrote:
> 2015-08-19 2:46 GMT+02:00 Solar Designer <solar@...nwall.com>:
> > On Tue, Aug 18, 2015 at 01:35:47AM +0200, Agnieszka Bielec wrote:
> >> a@...l:~/f/run$ ./john --test --format=argon2d
> >> Will run 8 OpenMP threads
> >> Benchmarking: argon2d [Blake2 AVX]... (8xOMP)
> >> memory per hash : 1.50 MB
> >> using different password for benchmarking
> >> DONE
> >> Speed for cost 1 (t) of 1, cost 2 (m) of 1536, cost 3 (l) of 1
> >> Many salts:     7760 c/s real, 971 c/s virtual
> >> Only one salt:  7808 c/s real, 976 c/s virtual
> >
> > I assume it's just a temporary glitch that "Many salts" appeared
> > slightly slower than "Only one salt" here.  They should be almost the
> > same, or "Many salts" very slightly better.  In fact, once you're done
> > debugging these formats, you'll need to set BENCHMARK_LENGTH to -1 to
> > suppress these separate benchmark (there will be just one then: Raw).
> 
> I tested bcrypt and scrypt and the same situation
> 
> none@...e ~/Desktop/r/run $ ./john --test --format=bcrypt
> Will run 8 OpenMP threads
> Benchmarking: bcrypt ("$2a$05", 32 iterations) [Blowfish 32/64 X2]...
> (8xOMP) using different password for benchmarking
> DONE
> Speed for cost 1 (iteration count) of 32
> Many salts:     6096 c/s real, 768 c/s virtual
> Only one salt:  6225 c/s real, 782 c/s virtual

This might be CPU clock frequency scaling being slow to kick in (un-idle
your CPU), or other activity on the system being slow to calm down after
you've just started john.  You may try running longer benchmarks, e.g.
use "--test=10".

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ