3 ms·
> Modern password cracking rigs with multiple GPUs can try out billions of hashes a second. If you know the salt or blinding factor, you can often recover the p
by madacol 7y ago
> Modern password cracking rigs with multiple GPUs can try out billions of hashes a second. If you know the salt or blinding factor, you can often recover the password.
Isn't that what the rounds protects from?
- MattPalmer1086 7y agoYou mean doing multiple rounds of hashing, like PBKDF2? There are some better algorithms than that now, but yeah, trying to slow down the computation required to crack the password is a useful defence.
- madacol 7y agoYeah, any way of increasing the cost factor, whether is PBKDF2 rounds, salt rounds in bcrypt, or just a pepper
- MattPalmer1086 7y agoThe thing is, if the server is already doing all that good stuff with your password, then you're already as well protected as you can be with the current methods. If it's not, then it probably won't be implementing your protocol either! I agree that the current methods could be massively improved.
- madacol 7y agoIn the supposed scenario that the server sucks, and it stores directly whatever you sent them, no rounds, no salt, nothing, what you are left with, is whatever protection you did on the client side, so I'm thinking doing the rounds client-side. Now that I'm thinking about it, I don't know how practical it is to do the rounds on a low-spec device like a cheap android