3 ms·
Something I've never understood is why we don't hash the password on the client before sending it to the server, and again on the server. This prevents the serv
by gpm 8y ago
Something I've never understood is why we don't hash the password on the client before sending it to the server, and again on the server. This prevents the server from knowing your password (assuming it's a good one) with no real drawbacks that I can see.
- Ar-Curunir 8y agoThis provides no real defence against dictionary attacks; the attacker's work just doubles.
- gpm 8y agoNo, it doesn't. It does however provide defense against taking over the server, stealing everyone's passwords, and using them on other servers. I'm assuming, and I suppose I should have stated above, that the first hash is salted with something like the domain name. Even if not it provides the same level of protection for password generation schemes.
- deleted 8y ago[deleted]
- caf 8y agoBecause then the hash of the password becomes equivalent to a password - a malicious actor that learns the hash of the password can just use that to log in to the service (since they can just choose to send it to the server).
- gpm 8y agoYou're absolutely right. But it means that they can't use the password to build a dictionary, to log in to other services, etc. (Assuming the password is complex enough that the hash isn't reversible)