4 ms·
Hash the password locally (you are serving JavaScript over SSL right?) and only send the SHA256.
by XorNot 10y ago
Hash the password locally (you are serving JavaScript over SSL right?) and only send the SHA256.
- jensvdh 10y agoNever trust the client.
- XorNot 10y agoThis isn't about trusting the client: it's about your endpoint being able to only accept a SHA256 hash sum from the client (thus: length limited) while allowing the user to input arbitrarily long passwords. They hash in the browser: the only way they can mess with it by producing silly outputs, but that only hurts them.
- libeclipse 10y agoI can't think of any security implications of hashing on the client-side. What's your thinking?
- fnordsensei 10y agoDoes salting work if you hash in the browser?
- libeclipse 10y agoWell in this case the hash would be passed to Bcrypt or Scrypt, which have built in salt support, so client side salting wouldn't matter.
- shawnz 10y agoIf the hashes are leaked, you could log in with them.
- XorNot 10y agoWell serverside you store them as plaintext equivalents - i.e. salt+hash the hash. So a leak doesn't leak the user-side.
- zeveb 10y agoThat would lock out anyone who chooses not to execute your JavaScript. Requiring me to trust your code in order for you to decide whether or not to trust me is asking too much.
- 0xfeba 10y agoHow would you know that the hash is of a password of sufficient entropy?