Yeah anyone not using randomly generated passwords at this point is just fucking up. I know exactly three of my passwords: the one for my email, the one for my password manager, and the one I’m likely to give out (streaming services and such). The worst anyone can do with the third is cancel my Disney+ or something, and it’s really only given to my mom and sisters.
Well this was a JWT compromise, I think, but even still people use really bad passwords all the time. A salt is stored with the user record. The salt’s job is to invalidate rainbow tables. If you have a collection of a million bad passwords you can check them all salted in a second or two. Obviously that’ll depend on the hashing algorithm to an extent.
Yeah anyone not using randomly generated passwords at this point is just fucking up. I know exactly three of my passwords: the one for my email, the one for my password manager, and the one I’m likely to give out (streaming services and such). The worst anyone can do with the third is cancel my Disney+ or something, and it’s really only given to my mom and sisters.
Is salting password hashes so unknown that neither the lemmy devs nor the kbin dev(s?) have implemented it?
Well this was a JWT compromise, I think, but even still people use really bad passwords all the time. A salt is stored with the user record. The salt’s job is to invalidate rainbow tables. If you have a collection of a million bad passwords you can check them all salted in a second or two. Obviously that’ll depend on the hashing algorithm to an extent.