phc-discussions - Re: [PHC] Re: Initial hashing function. Feedback welcome

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: <CA+aY-u7CA=AxT=ohjHwdDcd-gH2W5H4GJ-+cHcZn+crL1Chjhg@mail.gmail.com>
Date: Thu, 2 Jan 2014 15:02:26 +0000
From: Peter Maxwell <peter@...icient.co.uk>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Re: Initial hashing function. Feedback welcome

On 2 January 2014 14:44, Bill Cox <waywardgeek@...il.com> wrote:

>
>
> Running multiple copies of memmove shows my system seems to handle about
> 23GB/s of memory bandwidth.  Two copies of keystretch achieve about 13GB/s.
>  It's not maxing out memory bandwidth, but it's getting there...
>

Surely you do not want to max-out memory bandwidth, that's more a problem
than a benefit is it not?  For example, password checks are but a small
proportion of what an average web-server must do.

Content of type "text/html" skipped