Earlier quoted context omitted.
> It means that the server never actually knows your password If the client is hashing it without a salt the server could simply check a Rainbow table ( https://en.wikipedia.org/wiki/Rainbow_table ) to know which password it is. For short inputs this could be trivial.
Sure, but I still think this is preferable to sending the password in clear text even over HTTPS. You're trusting the server doesn't do anything with the password and immediately hashes it, but it might not. It might store it, or even if it doesn't, your password will stick around in RAM for an indeterminate amount of time. If the server is compromised in any way, passwords could be exfiltrated. Companies are, someti…
My point is in both cases the server has access to the password. As I mentioned, without salt the server can get the original password (by checking the pre-computed rainbow table of hashes up to n length), so the trust issue is the same.
If this is slightly better (more obfuscated) or the same thing + a false sense of security is debatable, but I could agree.