|
Posted by John Bokma on June 10, 2006, 5:25 pm
Please log in for more thread options
> Google searches have helped me understand that MySql has changed their
> password scheme for users starting at version 4.1. And, I pulled the
> below snippet that lists the suggested ways to resolve this problem.
> If I want to pursue the option described in bullet number 1 - what do
> I need to upgrade? I've looked all over and that seems to be missing
> from all the discussions I can find. I'd appreciate any help here.
With a) a new driver is required I guess since the DBI driver acts like a
client. I would recommend to give c) a try.
> ------------------------------------------------------------
> To solve this problem, you should use one of the following approaches:
>
> a.. Upgrade all client programs to use a 4.1.1 or newer client
> library.
>
> b.. When connecting to the server with a pre-4.1 client program, use
> an
> account that still has a pre-4.1-style password.
>
> c.. Reset the password to pre-4.1 style for each user that needs to
> use a
> pre-4.1 client program. This can be done using the SET PASSWORD
> statement and the OLD_PASSWORD() function:
>
> mysql> SET PASSWORD FOR
> -> 'some_user'@'some_host' = OLD_PASSWORD('newpwd');
> Alternatively, use UPDATE and FLUSH PRIVILEGES:
>
> mysql> UPDATE mysql.user SET Password = OLD_PASSWORD('newpwd')
> -> WHERE Host = 'some_host' AND User = 'some_user';
> mysql> FLUSH PRIVILEGES;
> Substitute the password you want to use for "newpwd" in the preceding
> examples. MySQL cannot tell you what the original password was, so
> you'll need to pick a new one.
--
John Bokma Freelance software developer
&
Experienced Perl programmer: http://castleamber.com/
| 
XML Sitemap