phc-discussions - Re: [PHC] pufferfish

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <5334E498.7080908@bindshell.nl>
Date: Thu, 27 Mar 2014 19:55:20 -0700
From: Jeremi Gosney <epixoip@...dshell.nl>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] pufferfish

On 3/27/2014 6:35 PM, Bill Cox wrote:
> On Thu, Mar 27, 2014 at 9:09 PM, Bill Cox <waywardgeek@...il.com> wrote:
>> I like PufferFish the way it is, but as Alexander pointed out, when
>> you bust out of L1 cache, performance drops.  When you bust out of L3
>> into DRAM, if I read the code correctly, performance will drop a ton.
>> I'd be a hypocrite for not suggesting that you take his advice and
>> implement the wandering 4KiB window in the 2^cost loop.  Over half of
>> my submission is built on ideas he suggested.  I just hope there can
>> be some way for him to formally "win" regardless of which submission
>> built on his ideas wins.
>>
>> I give myself credit for knowing good ideas when I see them.  The
>> wandering 4KiB window seems like a winner to me.
>>
>> Bill
>
> On the other hand, taking Alexander's advice is how I managed to PO my
> boss and fail to sleep for more than about 4 hours a night for three
> months.  PufferFish is good.
>
> Bill


If everyone did what Alexander is doing, there wouldn't be any point in
having a competition ;)

Seriously though, it's not that it's a bad idea, it's that I'm already
committed to this design. Provided how close the deadline is, and how
much work I still have left to do to prepare my submission, I don't
really have time to even begin to think about how I would implement such
a feature.

That said, if anyone wants to fork the current reference implementation
and play around with implementing this idea, and submit a pull request,
I just might appreciate it greatly.

Jeremi