News for hackers. Stuff that matters.
Re:We replaced passwords with something worse by AndroTux on Thursday August 07, 2025 @02:45AM (#44821337)
You should never store passwords anyways. You store hashes. I don’t see the issue. If you don’t trust yourself to keep a hash, maybe don’t store user information at all.
Re:We replaced passwords with something worse by benrutter on Thursday August 07, 2025 @03:07AM (#44821462)
That's still not perfect though!

Most leaked passwords online come initially from leaked hashes, which bad actors use tools like hashcat to crack.

If your user has a password like "password123" and the hash gets out, then the password is effectively out too, since people can easily lookup the hash of previous cracked passwords like "password123".

Re:We replaced passwords with something worse by csnover on Thursday August 07, 2025 @03:30AM (#44821604)
No. This is why salts[0] are used.

[0] https://en.wikipedia.org/wiki/Salt_(cryptography)

Re:We replaced passwords with something worse by incorrecthorse on Thursday August 07, 2025 @04:47AM (#44822152)
And compute-intensive hash functions. Computers this day are powerful enough to hashcat each individual pwd+salt if a fast hashing function is used.
Re:We replaced passwords with something worse by integralid on Thursday August 07, 2025 @04:52AM (#44822189)
This is how it should be done. But it still doesn't protect users fully, because attacker can try to brute-force passwords their interested in. It requires much more effort though.
Re:We replaced passwords with something worse by Macha on Thursday August 07, 2025 @03:32AM (#44821610)
Salting already fixed this decades ago, and most modern password libraries will automatically generate and verify against a hash like <method>$salt$saltedhash if you use them instead of rolling your own.