(issue imported from #M4139)
Updated by Stefan Strasser about 14 years ago
That is not a bug, I think it is the same behaviour as with the backend login.
Updated by Christian Toffolo about 14 years ago
If it is possible, I suggest to switch to a server-side encryption.
Updated by Andreas Wolf about 14 years ago
Well, the client-side encryption is the key to a secure submission of the password. It would be highly insecure to send passwords over an unencrypted connection.
What happens on the client is the following:
1) The password ist md5-hashed.
2) The username is prepended and a challenge is appended to the hash from 1).
3) This value is hashed again and then sent to the server.
The server repeats step no. 2 with the encrypted value from the database. So neither the clear-text nor the hashed passwort are sent over the network. The challenge is a md5-hash of the time and some other value, so it is more or less random and not predictable. And it has to be stored on the server, so even if someone knows the hash-value of the password, he would also need a correct challenge - this wouldn't be a problem, but ok...