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: <CAHOTMVK0wKGdqPKppre2XNg2Rj1g6MpMgkjfAGbZrVpqNbcywg@mail.gmail.com>
Date: Fri, 14 Mar 2014 00:38:10 -0700
From: Tony Arcieri <bascule@...il.com>
To: Jeremy Spilman <jeremy@...link.co>
Cc: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] "Why I Don't Recommend Scrypt"

On Thu, Mar 13, 2014 at 11:16 PM, Jeremy Spilman <jeremy@...link.co> wrote:

>  It's probably so easy to enumerate users on a system through timing,
> it's almost worth giving up on the premise, and just provide a descriptive
> login error message.
>

Security is hard, let's go shopping! Well, hopefully if we actually give it
a decent go we can do better than Snapchat, or AT&T.

But seriously, I think the real solution here is server relief protocols.
It should be possible to use some fancy pants scrypt-like algorithm without
overwhelming your infrastructure by moving most of the computation to the
client.

-- 
Tony Arcieri

Content of type "text/html" skipped