oh i forgot to mention,
the new passwords are stored in the database already. you need to reset
the password with the OLD_PASSWORD() function. they detail that in the
documentation
b
Brandon Ooi wrote:
this refers to a new password scheme used in mysql 4.1 and above. see
here to fix this...
http://dev.mysql.com/doc/refman/5.0/en/old-client.html
b
John Hoover wrote:
I've been running MySQL 4.0.20 on Mac OS 10.3.5 for some months and
had been working on a custom client. It was working well until I
upgraded by computer to 10.4.3 and MySQL to 5.0.18. My client can not
longer connect - I get an error message: "Client does not support
authentication protocol requested by server."
I assumed this was due to the changes in the password hashing
function since version 4.0, so I used MySQL Administrator to add the
following my.cnf file in /etc.
[mysqld]
#This option makes InnoDB to store each created table into its own
.ibd file.
innodb_file_per_table
#Don't allow new user creation by the user who has no write
privileges to the mysql.user table.
safe-user-create
#Use old password encryption method (needed for 4.0 and older clients).
old-passwords
After restarting the database, I still could not connect. I added the
same cnf file to mysql/data and restarted the database again. Again,
I was unable to connect.
Can anybody tell me what I'm doing wrong here? Also, how can I find
out whether mysqld is actually using the cnf settings?
Thanks,
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]