News for hackers. Stuff that matters.
Re:Security Checklist by tptacek on Sunday March 20, 2016 @03:13PM (#11324187)
No. The reason not to use Argon2 is that it doesn't have great library support yet. Password hashes don't really fail like ciphers do. Nothing that is discovered in Argon2 is going to make it worse than PBKDF2, and using PBKDF2 is just fine if that's all you've got.
Re:Security Checklist by dsacco on Sunday March 20, 2016 @04:58PM (#11324625)
>> and using PBKDF2 is just fine if that's all you've got.

Yeah, people spend way too much time wondering if they should use scrypt, bcrypt, PBKDF2, etc. There are legitimate differences, but unless you know those ahead of time it's almost certainly better to just choose one instead of waffling around.

Re:Security Checklist by technion on Sunday March 20, 2016 @11:29PM (#11326033)
The reference library we do have looks set to make further breaking changes[0], which complicates this further.

[0] https://github.com/P-H-C/phc-winner-argon2/pull/119/files

Re:Security Checklist by devit on Monday March 21, 2016 @06:27AM (#11327149)
Huh?

A password hash could happen to be reversible, or could map lots of passwords to the same value.

Re:Security Checklist by tptacek on Monday March 21, 2016 @07:59AM (#11327447)
No, neither of those things are going to happen.

It might happen if you designed a password hash from first principles, but that is not how Argon2 was designed, or, really, any of the Password Hashing Contest finalists. They're built on top of existing crypto primitives.