phc-discussions - Re: [PHC] "Why I Don't Recommend Scrypt"

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: <CAHOTMVL-qUAZBeLd+_HsHpCPF36zhn6GNE8BWed5jRFz5DtZjA@mail.gmail.com>
Date: Thu, 13 Mar 2014 10:41:33 -0700
From: Tony Arcieri <bascule@...il.com>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] "Why I Don't Recommend Scrypt"

On Thu, Mar 13, 2014 at 10:39 AM, Peter Maxwell <peter@...icient.co.uk>wrote:

> That depends on what you consider a high rate of password verification and
> RAM-limited.  Amazon is currently advertising their "m3.large" cloud
> instance - which I presume is fairly standard - as having 7.5Gb RAM.  So
> lets presume our hypothetical standard sysadmin is running a webserver with
> PHP
>

Yeah, guess we're off in a different universe, and a PHP-free one at that
;) We run our own bare metal, and I believe our minimum server deployment
has 64GB of RAM, but don't quote me on that

-- 
Tony Arcieri

Content of type "text/html" skipped