According to that page, if you start the 4.1 server with --old-passwords, it is supposed to generate short password hashes rather than long, so you shouldn't have to shorten the password column (though that works). Is it possible you didn't restart, or perhaps started with --old-password (missing the s on the end)?
Without using --old-passwords, you should still be able to create short password hashes using the OLD_PASSWORD() function, like this
mysql> UPDATE user SET Password = OLD_PASSWORD('mypass')
-> WHERE Host = 'some_host' AND User = 'some_user';
mysql> FLUSH PRIVILEGES;Michael
jamie murray wrote:
If you resize the password column to what it was pre 4.1 it will store a
hash the same length as the old algo used to produce and users will be able
to log in just fine.
Michael Stassen pointed me to this link
http://www.mysql.com/doc/en/Password_hashing.html>. and it has a number of
work arounds.
----- Original Message ----- From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 08, 2004 5:01 PM
Subject: Re: 4.1.1 --old-paswords & 4.0.X clients
It would be nice to dump the confidentiality statement. Unfortunately, our mail server adds it to the message as it's sent to the internet -- I have no control over it. It's alright though since my message is "intended to be for the use of the entity named above." In this case, the MySQL list community!
As for the --old-password, it's looking to me like it's not that easy. I think but don't know yet, that any new password created on the 4.1.1 server -- even with --old-passwords set -- uses the new algorithm. My reading of the documentation, until somebody tells me, or I can prove otherwise, is that --old-passwords only allows previously existing passwords to be used -- i.e. only when an existing 4.0 server is upgraded to 4.1. Any new passwords created on the new server must use the new algorithm -- apparently even if you are using a 4.0 client log in as root to create the password. At least, that's what is happening to me.
Thanks.
Randolph "Randy" L. Chrismon [EMAIL PROTECTED] Ph. 732-452-7610
Victor Medina <[EMAIL PROTECTED]> 01/08/2004 15:14
To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: 4.1.1 --old-paswords & 4.0.X clients
It did change, but you can still use the old protocol by adding --old-passwords option to the mysqld or adding old-passwords option to the [mysqld] group in my.cnf, using this, old clients will be able to connect to 4.1 series servers without probs :)
By the way, i am not quite sure, but you should remove the down legal note, i think the mysql list is public and free to every one to use and quote, so while posting here it is better to remove the note, maybe someone at mysql.com could confirm this?
Best Regards On Thu, 2004-01-08 at 15:45, [EMAIL PROTECTED] wrote: I have a workstation that I set up as a 4.0.16 server to prove to myself that I could use MySQL for an application we are developing. Now, for beta
testing, I set up a new 4.1.1 server on a real server box. I did not upgrade the workstation with the 4.0.16 server. In setting up the new server, I ran the mysql_fix_privilege_tables script and restarted the server with the --old-passwords option. I then logged in locally as root and created a new user account for me from my OTHER workstation with the 4.0 client. Unfortunately, as long as my account on the new server has a password, I can't log in. I get the old standby, "Client does not support authentication protocol requested by server; consider upgrading MySQL client." I went back to the documentation and it slowly dawned on me that it was speaking strictly of an UPGRADE to an existing installation when it
talked about old passwords and the like. Consequently, I am beginning to suspect that I cannot install a new 4.1.1 server and still use 4.0 clients. Is this correct or am I missing something (wish I could say that was unlikely ;->)?
Thanks
Randolph "Randy" L. Chrismon [EMAIL PROTECTED]
Confidentiality Note: This message and any accompanying attachments contain information from the law firm Fragomen, Del Rey, Bernsen & Loewy, P.C. which is confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the
intended recipient, be aware that any disclosure, copying, distribution or
use of the contents of this information is prohibited. If you have received this e-mail in error, please notify our offices immediately, by telephone at 212-688-8555, or by e-mail at [EMAIL PROTECTED] --
|...........................................................| |____ _____ ____ _ |Victor Medina M | |\ \ \| ____| _ \ / \ |Linux - Java - MySQL | | \ \ \ _| | |_) / _ \ |Dpto. Sistemas - Ferreteria EPA | | / / / |___| __/ ___ \ |[EMAIL PROTECTED] | |/_/_/|_____|_| /_/ \_\|ext. 325 | | |geek by nature - linux by choice | |...........................................................|
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
