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 20:23:52 +0000
From: "Brian Matthews (brmatthe)" <brmatthe@...co.com>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] "Why I Don't Recommend Scrypt"

On 3/13/14 11:01 AM, "Tony Arcieri" <bascule@...il.com<mailto:bascule@...il.com>> wrote:

On Thu, Mar 13, 2014 at 10:56 AM, Brian Matthews (brmatthe) <brmatthe@...co.com<mailto:brmatthe@...co.com>> wrote:
Oops, I was looking at the wrong stat, the peak is only about 400 (today, it grows over time). It's not a classic login (like at a bank say), it's lighter weight

What does this even mean?

The light weight part? It's not relevant to this list, just noting that it's a less resource intensive login overall than what one might think of as a normal web login. The relevant part to this list is of course is that an authentication is done, so a password hash is performed.

Brian

Content of type "text/html" skipped