3 ms·
Unfortunately, like NaCl, it's missing 2 common and critical functions: 1. Password-based key derivation 2. Persistent key storage So developers are s
by missinginaction 14y ago
Unfortunately, like NaCl, it's missing 2 common and critical functions:
1. Password-based key derivation
2. Persistent key storage
So developers are still expected to work out those 2 problems and will reliably screw them up.
- bascule 14y agoSodium will ship whatever algorithm wins the upcoming Password Hashing Competition: https://password-hashing.net/ https://password-hashing.net/
- mpyne 14y agoI thought the first one was solved at least 3 different ways over now, and that we should just pick one of [bcrypt, PBKDF2, scrypt]?
- jedisct1 14y agoSee this excellent presentation by Solar Designer on this very topic: http://www.openwall.com/presentations/Passwords12-The-Future-Of-Hashing/ http://www.openwall.com/presentations/Passwords12-The-Future...
- tptacek 14y agoThat 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.
- tel 14y agoOkay, that's where I'm at these days. What is the right way to do persistent key storage?
- qznc 14y agoPersistence means storing it in a file or database. Not a job for library of primitives.
- kzrdude 14y agoI don't think NaCl keys are suitable for persistance. It seems to require absolute uniqueness of nonces.