3 ms·
The downside to this is that it requires the server to store the password unencrypted and unhashed. The server must have access to the original password to has
by mfenniak 18y ago
The downside to this is that it requires the server to store the password unencrypted and unhashed. The server must have access to the original password to hash with the random number for comparison. In my opinion, this wouldn't be an improvement in the overall security of the system.
Avoid sending a plaintext password by using HTTPS. It's the easiest way.
- hsiung 18y agoYou store the password hashed with a salt in the database (just keep track of the salt you used). The server can send the salt to the client, in addition to the random number. So the client is performing two hashes: md5(md5(password+salt)+random_token).