4 ms·
Even then it's better than nothing. If every company used different salt, rainbow tables would have to be completely regenerated for each company. (This is sti
by kstrauser 6y ago
Even then it's better than nothing. If every company used different salt, rainbow tables would have to be completely regenerated for each company.
(This is still awful, because then two users with the same password would have the same digest. If you know that joe@example.com has password "badpass", and jane@example.com has the same hashed password, then hers is also "badpass". So use randomly per-user salts, gang! Even better, pick a tested implementation of PBKDF2 or Argon2 and use that implementation. Don't roll your own crypto!)
But still, it's better than nothing.
- rileymat2 6y agoOh, yeah, I agree, it is better than nothing. Just pointing out that I have seen conditions where the article is not terribly wrong in its statement. Things like bcrypt are nice because they take care of that for you.
- deleted 6y ago[deleted]
- _trampeltier 6y agoWhy not just use joe@example.com as part of the salt? So every user has a different salt.
- deleted 6y ago[deleted]
- stickfigure 6y agoUsernames and email addresses change.
- ryanlol 6y agoDoes anyone actually use rainbow tables to crack password hashes anymore with GPUs being so fast?
- kstrauser 6y agoAn O(1) "is this hash known?" lookup is going to be faster than any GPU code.
- ryanlol 6y agoIn a world with unlimited IO throughput and very few hashes to crack, yeah. Discussion from 2017: https://hashcat.net/forum/thread-6219.html https://hashcat.net/forum/thread-6219.html From 2018: https://security.stackexchange.com/questions/186953/cracking-passwords-via-hashcat-or-rainbow-tables-which-is-faster https://security.stackexchange.com/questions/186953/cracking... GPUs are much faster now. I doubt you’ll find many people using rainbowcrack or similar tools in 2021. OTOH https://www.rainbowcrackalack.com/ https://www.rainbowcrackalack.com/
- kstrauser 6y agoHuh, TIL. Thanks for the links.
- mjevans 6y agoWhat about taking results from one leak's reversed passwords and applying it to all future hash leaks? It's the same logic as applying well known target data like birthdays, anniversaries, etc.
- kstrauser 6y agoSalting makes that nearly impossible.
- mjevans 6y agoSalting makes each crack take either it's own rainbow table or other methods. I was talking about _reversed_ passwords, guesses that fulfill the algorithm. Bonus points if they look like names, words, etc, but even random junk might just be a pwgen password.