Re:Hell Is Overconfident Developers Writing Encryption Code
by lelanthran on Saturday February 01, 2025 @11:27AM
(#42899559)
My understanding of bcrypt math is that the input to the algorithm is a random salt and a message, with the output being a hash.
I believe the actual implementation gives two output fields as a single value, with that value containing the salt and the hash.
This might be why we appear to be talking past each other - I consider bcrypt to be a salted hash because it takes a salt in the inputs and produces a hash in the output.
The fact that the output also contains the salt is, in my mind, an implementation detail.
Re:Hell Is Overconfident Developers Writing Encryption Code
by tptacek on Saturday February 01, 2025 @01:31PM
(#42900792)
Yes. We aren't talking past each other anymore. If you aren't composing a "salted hash" out of a cryptographic hash function and a salt, but are instead using bcrypt, scrypt, PBKDF2, or Argon2, you have nothing to worry about. Just to complete your understanding: the salt --- randomizing the hash --- has very little to do with what makes bcrypt a good password hash.
You'll avoid this confusion in the future if you don't refer to bcrypt as a "salted hash". Salted hashes are the technology bcrypt was invented to replace.
Re:Hell Is Overconfident Developers Writing Encryption Code
by noduerme on Thursday February 06, 2025 @08:55AM
(#42962309)
OP here: I am using bcrypt to hash passwords, but I struggle to understand how not salting i.e. not randomizing it against a stored secret would still be safe for storing short strings. Be that as it may, I'm glad to hear I'm not doing anything horribly wrong when building login systems.
What you can't do is use SHA2 with a random salt and call it a day.