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  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, 9 Mar 2014 08:14:30 +0400
From: Solar Designer <solar@...nwall.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Are password trailing 0's a problem?

On Sat, Mar 08, 2014 at 10:59:58PM -0500, Bill Cox wrote:
> However, while this flaw is certainly not a critical weakness, and
> obviously Escript in compatibility mode needs to continue using PBKDF2
> as-is, for non-compatible mode, or entirely new password hashing
> systems, should we live with such flaws or try to eliminate them?

We should try to eliminate them.

Regarding your idea re: all PHC submissions doing it in the same way,
I'm not so sure.  In each case, the choice might be affected by other
crypto primitives and constructions that a given PHC submission would
use anyway, so that its total complexity is less.  For escrypt, this is
a reason for its non-compat modes to reuse PBKDF2 anyway, just working
around its shortcomings.

Alexander

Powered by blists - more mailing lists