4 ms·
> Hash passwords using a real pbkdf like argon2 in JS or native code client-side, using sensible mem-/cpu-/gpu-fpga-/asic-hard params, because passwords should
by zamadatix 8y ago
> Hash passwords using a real pbkdf like argon2 in JS or native code client-side, using sensible mem-/cpu-/gpu-fpga-/asic-hard params, because passwords should never go over the wire in any form.
If you're sending the hash on behalf of the password... doesn't that just turn the hash into password? In either case if you get the info that's all you need to send to the server for auth.
- paulddraper 8y agoYou could hash the password again on the server, preserving the property that getting database info doesn't compromise logins. But you would also have added property that the password is never processed at all server-side. IDK if that latter item is actually significant.