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: <CAHOTMVJtC+UkcP72MnkaU_oyiuQ4c5xMp0YvhiTveuKoEMdY6w@mail.gmail.com>
Date: Thu, 13 Mar 2014 11:45:39 -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 11:42 AM, Patrick Mylund Nielsen <
patrick@...rickmylund.com> wrote:

> I never bought that argument. You can be DoS'ed in many, many ways. The
> solution is exponential backoff and similar, not to (again) compromise on
> the security of the password digests.
>

Exponential backoff based on what, source IP address? What if you're being
DDoSed?

Account name? If you don't compute a password hash even for invalid account
names, you're vulnerable to user enumeration attacks.

-- 
Tony Arcieri

Content of type "text/html" skipped