lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 27 Mar 2014 20:52:32 -0400
From: Bill Cox <>
Subject: Re: [PHC] pufferfish

On Thu, Mar 27, 2014 at 8:22 PM, Solar Designer <> wrote:
> On Thu, Mar 27, 2014 at 08:04:47PM -0400, Bill Cox wrote:
>> I had the same thought that doing the two block-size thing would make
>> PufferFish like Escrypt and TwoCats.  Not doing it seems like a
>> critical limitation.  PufferFish is cool.  I think it would be cooler
>> with one more outer loop, though it threatens the simplicity that I
>> like about it.
> Right.
> I had actually considered revising the original bcrypt to introduce that
> "outer loop", and I felt that it could be done without it appearing as
> an extra loop.  bcrypt already has its 2^cost loop - that one loop could
> be revised to move the 4 KiB region across a larger arena and to XOR (or
> whatever) it with random 4 KiB regions in the already-written portion of
> the arena.
> Alexander

+1 for this solution.  That would make PufferFish competitive.


Powered by blists - more mailing lists