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]

Date: Thu, 13 Mar 2014 14:42:42 -0400
From: Patrick Mylund Nielsen <patrick@...rickmylund.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 2:34 PM, Tony Arcieri <bascule@...il.com> wrote:

> On Thu, Mar 13, 2014 at 11:30 AM, Patrick Mylund Nielsen <
> patrick@...rickmylund.com> wrote:
>
>> I think this is the closest to a good argument against expensive
>> functions that you get
>>
>
> The real argument against expensive functions is DoS (which, as it were,
> was not mentioned in the blog post)
>
>
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.

Has anyone who actually implemented automatic logouts for e.g. 10 failed
logins ever experienced a DoS because of their password authentication
function? Everybody brings it up, but nobody seems to have experienced it.

Content of type "text/html" skipped