Re:Introducing Sodium, a new cryptographic library
by missinginaction on Wednesday March 06, 2013 @09:18PM
(#5335568)
Unfortunately, like NaCl, it's missing 2 common and critical functions:
So developers are still expected to work out those 2 problems and will reliably screw them up.
[ Parent
| on HN ]
Re:Introducing Sodium, a new cryptographic library
by bascule on Wednesday March 06, 2013 @09:22PM
(#5335592)
Sodium will ship whatever algorithm wins the upcoming Password Hashing Competition:
Re:Introducing Sodium, a new cryptographic library
by mpyne on Wednesday March 06, 2013 @11:21PM
(#5336061)
I thought the first one was solved at least 3 different ways over now, and that we should just pick one of [bcrypt, PBKDF2, scrypt]?
Re:Introducing Sodium, a new cryptographic library
by tptacek on Thursday March 07, 2013 @12:16AM
(#5336238)
That still really is the answer for password hashes.
The right ordering is scrypt, bcrypt, PBKDF2, but even if you choose PBKDF2 you're still worlds better than salted hashes.
It makes sense for NaCL/Sodium to just pick one, though, and it makes sense for the choice to come from the hash contest.
Re:Introducing Sodium, a new cryptographic library
by jedisct1 on Thursday March 07, 2013 @12:10AM
(#5336219)
See this excellent presentation by Solar Designer on this very topic: http://www.openwall.com/presentations/Passwords12-The-Future...
Re:Introducing Sodium, a new cryptographic library
by tel on Thursday March 07, 2013 @01:21AM
(#5336423)
Okay, that's where I'm at these days. What is the right way to do persistent key storage?