Good-day all,
I need help setting the passwords in my database to the new 4.1 authentication style released with the MySQL .Net Connector version 6.6.4. Based on the thread here (http://bugs.mysql.com/bug.php?id=66647) apparently Oracle decided to drop the old password encryption method, as it was insecure. This has brought my development in Visual Studio to a halt as I can't connect to the MySQL database on my ClearOS box (since it uses the old_password authentication method).
They suggested that I do something like this:
But all my attempts within the database returns the following:
Are you guys even aware of this? If so, can somebody render any assistance?
//Kismet
I need help setting the passwords in my database to the new 4.1 authentication style released with the MySQL .Net Connector version 6.6.4. Based on the thread here (http://bugs.mysql.com/bug.php?id=66647) apparently Oracle decided to drop the old password encryption method, as it was insecure. This has brought my development in Visual Studio to a halt as I can't connect to the MySQL database on my ClearOS box (since it uses the old_password authentication method).
They suggested that I do something like this:
set password for 'oldpassuser'@'localhost' = password( '123' )
But all my attempts within the database returns the following:
Query OK, 0 Rows Affected (0.00 secs)Are you guys even aware of this? If so, can somebody render any assistance?
//Kismet
In Database
Share this post:
Responses (1)
-
Accepted Answer
Hello again,
I managed to resolve the problem after reading through this article on the MySQL site (http://dev.mysql.com/doc/refman/5.5/en/password-hashing.html). Here's what I did - hope it helps somebody:
The script they gave wasn't working for me. So I did the following:
Using MySQL Workbench I
1. Changed the server variable for old_passwords to 0 by unchecking it.
2. Deleted the user accounts that had the old 16-byte hashed passwords.
3. Restarted the server.
4. Recreated the users - and this time passwords were hashed to 41-bytes.
My application is now able to connect to the database without a problem. Thanks again.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »