4.0 mysql client vs 4.1 installation
This is not a question, rather just some information I wanted to post in case someone else hits it and searches the lists. I do a lot of straight command line connecting using the mysql.exe client for windows. Aside from my other challenges with getting users set up properly, I ran into another one yesterday where I couldn't connect from my workstation, which was using a 4.0.18 mysql.exe (size=294,980). The error was pretty straightforward: ERROR 1250: Client does not support authentication protocol requested by server; consider upgrading MySQL client When I copied the mysql.exe file from my 4.1.1 alpha installation to my workstation, I could connect fine. The size for the 4.1.1 windows mysql.exe file is 974,992. From my testing so far, I haven't run into any backward-compatibility issues. Lou
Re: 4.0 mysql client vs 4.1 installation
Lou Wrote This is not a question, rather just some information I wanted to post in case someone else hits it and searches the lists. I do a lot of straight command line connecting using the mysql.exe client for windows. Aside from my other challenges with getting users set up properly, I ran into another one yesterday where I couldn't connect from my workstation, which was using a 4.0.18 mysql.exe (size=294,980). The error was pretty straightforward: ERROR 1250: Client does not support authentication protocol requested by server; consider upgrading MySQL client When I copied the mysql.exe file from my 4.1.1 alpha installation to my workstation, I could connect fine. The size for the 4.1.1 windows mysql.exe file is 974,992. From my testing so far, I haven't run into any backward-compatibility issues. Lou /Lou wrote There is another way to resolve that issue. Your problem existed because the password hash was lengthened as of 4.1 (which is why your pre 4.1.x client couldn't authenticate with the new server.) You can keep using a pre-4.1.x client or library (the window's ODBC drivers are at 3.51) by using the new (as of 4.1) function OLD_PASSWORD() to re-encrypt the user's password to the shorter (pre-4.1) hash. You really need read this for more details: http://dev.mysql.com/doc/mysql/en/Password_hashing.html It covers the PASSWORD() and OLD_PASSWORD() functions as well as the --old-passwords startup option in some depth. Pay close attention to the warnings about what works and doesn't when you are using mixed version authentication. Shawn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: 4.0 mysql client vs 4.1 installation
You can also use the `old-passwords` option in the my.cnf file. -Original Message- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: 5/4/04 1:09 PM Subject: Re: 4.0 mysql client vs 4.1 installation Lou Wrote This is not a question, rather just some information I wanted to post in case someone else hits it and searches the lists. I do a lot of straight command line connecting using the mysql.exe client for windows. Aside from my other challenges with getting users set up properly, I ran into another one yesterday where I couldn't connect from my workstation, which was using a 4.0.18 mysql.exe (size=294,980). The error was pretty straightforward: ERROR 1250: Client does not support authentication protocol requested by server; consider upgrading MySQL client When I copied the mysql.exe file from my 4.1.1 alpha installation to my workstation, I could connect fine. The size for the 4.1.1 windows mysql.exe file is 974,992. From my testing so far, I haven't run into any backward-compatibility issues. Lou /Lou wrote There is another way to resolve that issue. Your problem existed because the password hash was lengthened as of 4.1 (which is why your pre 4.1.x client couldn't authenticate with the new server.) You can keep using a pre-4.1.x client or library (the window's ODBC drivers are at 3.51) by using the new (as of 4.1) function OLD_PASSWORD() to re-encrypt the user's password to the shorter (pre-4.1) hash. You really need read this for more details: http://dev.mysql.com/doc/mysql/en/Password_hashing.html It covers the PASSWORD() and OLD_PASSWORD() functions as well as the --old-passwords startup option in some depth. Pay close attention to the warnings about what works and doesn't when you are using mixed version authentication. Shawn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 4.0 mysql client vs 4.1 installation
At 10:39 -0400 5/4/04, Lou Olsten wrote: This is not a question, rather just some information I wanted to post in case someone else hits it and searches the lists. I do a lot of straight command line connecting using the mysql.exe client for windows. Aside from my other challenges with getting users set up properly, I ran into another one yesterday where I couldn't connect from my workstation, which was using a 4.0.18 mysql.exe (size=294,980). The error was pretty straightforward: ERROR 1250: Client does not support authentication protocol requested by server; consider upgrading MySQL client When I copied the mysql.exe file from my 4.1.1 alpha installation to my workstation, I could connect fine. The size for the 4.1.1 windows mysql.exe file is 974,992. From my testing so far, I haven't run into any backward-compatibility issues. Lou Additional reading: http://dev.mysql.com/doc/mysql/en/Old_client.html http://dev.mysql.com/doc/mysql/en/Password_hashing.html http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.0.html -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
