Bug #8991 Missing options on how to solve the new password hashing problem
Submitted: 6 Mar 2005 15:00 Modified: 3 Oct 2008 18:33
Reporter: Eduardo Pérez Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version:4.1.10 OS:Any
Assigned to: CPU Architecture:Any

[6 Mar 2005 15:00] Eduardo Pérez
Description:
When connecting using an old client library to a new account in mysql-4.1.x there's this error displayed. I saw I had to recompile using the new client libraries but found that I just needed to downgrade the password hash.
I googled the problem and found the simpler fix.

How to repeat:
Use an old client library to connect to a newly created account in mysql-4.1.x

Suggested fix:
This patch gives a better problem explanation:
--- mysql-4.1.10/sql/share/english/errmsg.txt
+++ mysql-4.1.10/sql/share/english/errmsg.txt
@@ -267,7 +267,7 @@
 "Every derived table must have its own alias",
 "Select %u was reduced during optimization",
 "Table '%-.64s' from one of the SELECTs cannot be used in %-.32s",
-"Client does not support authentication protocol requested by server; consider upgrading MySQL client",
+"Client does not support authentication protocol requested by server; consider upgrading MySQL client or reset the password to pre-4.1 style http://dev.mysql.com/doc/mysql/en/old-client.html",
 "All parts of a SPATIAL index must be NOT NULL",
 "COLLATION '%s' is not valid for CHARACTER SET '%s'",
 "Slave is already running",
[3 Oct 2008 18:33] Konstantin Osipov
We do not plan to do anything about pre-4.1 passwords.
Thank you for your interest in MySQL.