phc-discussions - Re: [PHC] Native server relief support for password hashing in browsers

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: Sun, 19 Jan 2014 00:16:52 -0800
From: Larry Bugbee <bugbee@....com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Native server relief support for password hashing in browsers

On Jan 18, 2014, at 11:54 PM, Solar Designer <solar@...nwall.com> wrote:

> On Sat, Jan 18, 2014 at 01:14:32PM -0800, Tony Arcieri wrote:
>> On Sat, Jan 18, 2014 at 1:12 PM, Larry Bugbee <bugbee@....com> wrote:
>> 
>>> May I assume that if the pswd is hashed client side, two conditions need
>>> to be true: 1) javascript or other hashing support is available, and 2) the
>>> hash is passed in a secure tunnel
>> 
>> Yes
> 
> I'd say "secure tunnel" is orthogonal to "client-side hashing", as well
> as to "better password hashing" in general.  Any of these are somewhat
> nice to have even without the others, although of course a combination
> of them is usually preferable.
> 
> Alexander

I agree that my questions are borderline off-topic, but as an observer of the process I question the value of well protected passwords at rest if they can be siphoned off before they even get there.  Like so many problems in security, a balanced approach seems best.  

A good solution here is welcome but some quick reading suggested by Tony confirms my suspicions that there are arguably even weaker links.  Nevertheless, each link needs to be improved and the discussion here has been both interesting and enlightening.  Thank you all.