4 ms·
I kinda expected you to correct me. You can't help yourself can you. :) And that is a good thing. Thanks! Sorry I was not trying to give the entire recipe for
by spikels 13y ago
I kinda expected you to correct me. You can't help yourself can you. :) And that is a good thing. Thanks!
Sorry I was not trying to give the entire recipe for password handling. I was assuming a KDF with lots of iterations. But perhaps you could clear up one thing:
Assuming proper implementation (I know a big assumption) how is bcrypt better than PBKDF2 with lots of iterations using a good hash and salt? At some bcrypt cost and PBKDF2 iteration count wouldn't they be equally secure?
- tptacek 13y agoPBKDF2 is straightforward to accelerate in commercial off the shelf hardware, and bcrypt isn't. But both are fine. Neither are "salted hashes".
- spikels 13y agoI guess I had my terminology wrong you would know better. I always thought of PBKDF2 as simply "iterated hashing of a salted password".
- B-Con 13y agoYour mental model isn't necessarily wrong. The phrase "salted hash" generally refers to something more plain than PBKDF2. PBKDF2 is technically a "Key Derivation Function", but it can also be used as a "Password Hash Function". Password Hashes generally use a hash function and a salt, yes, but they also incorporate other important factors as well, commonly a work factor and some "hard" computational problem, so it's unfair to call them merely a salted hash. PBKDF2, along with password hashes in general, do indeed do everything a "salted hash" would do, but importantly, they also do more.