I wrote a Visual Basic application to sell that uses the .NET connector 6.6.6 for MySQL.
About 50% of my customers get the message:
"MySql – Authentication with old password no longer supported, use 4.1 style passwords"
I have found that if TOAD for MySQL is used on the workstation that needs to connect and the following commands are run the problem is solved:
SET SESSION old_passwords=0;
SET PASSWORD=PASSWORD('YOURDATABASEPASSWORD');
The CPANEL/PHPmyAdmin the users have access cannot make the change to the password and I cannot run the commands remote and make it work for my users.
This means that 50% of my customers have to download TOAD, learn how to use it and run it on maybe 10 databases before they can use my application.
Is there another solution or workaround for this problem?
Can I add some code to the application to avoid the error in the first place?
Is this a bug or just a problem?
About 50% of my customers get the message:
"MySql – Authentication with old password no longer supported, use 4.1 style passwords"
I have found that if TOAD for MySQL is used on the workstation that needs to connect and the following commands are run the problem is solved:
SET SESSION old_passwords=0;
SET PASSWORD=PASSWORD('YOURDATABASEPASSWORD');
The CPANEL/PHPmyAdmin the users have access cannot make the change to the password and I cannot run the commands remote and make it work for my users.
This means that 50% of my customers have to download TOAD, learn how to use it and run it on maybe 10 databases before they can use my application.
Is there another solution or workaround for this problem?
Can I add some code to the application to avoid the error in the first place?
Is this a bug or just a problem?