3 ms·
Hashing twice, on the client as well as on the server, won't introduce any security issues if the choice of algorithm is good, and it does further protect the u
by smolder 6y ago
Hashing twice, on the client as well as on the server, won't introduce any security issues if the choice of algorithm is good, and it does further protect the users password from being harvested from passive MITM'd SSL like it is on some corporate networks. (Yes I know MITM means they could rewrite the client to steal passwords, but that's work) If I was designing a password auth scheme that highly prioritized user security, I would hash both client and server side.
- Sir_Substance 6y ago>and it does further protect the users password from being harvested from passive MITM'd SSL like it is on some corporate networks. It might protect the password if the user is reusing it elsewhere, but it doesn't protect the account the password is securing during the intercepted transmission. The MITM attacker can just replay the hash.
- nucleardog 6y agoNo reason the server can’t provide a nonce for the login to salt the hash.
- withinboredom 6y agoAnd how would the server know the desalted hash?
- Sir_Substance 6y agoNow the server has to store the password in plain text so it can rehash with the new nonce every time.