.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
the tip.
Randy
Randolph "Randy" L. Chrismon
[EMAIL PROTECTED]
Ph. 732-452-7610
"jamie murray" <[EMAIL PROTECTED]>
01/08/2004 15:44
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
cc:
Subject:Re: 4.1.1 --old-paswords & 4.0.X
ork 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
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
you can still do a dump and restore, it works nicely. I think the
problem is that he users table changed. I have a 4.1 server running, i
just do a dump and restore from the old server to the new one. and added
the --old-password option.
Hope this helps!
On Thu, 2004-01-08 at 16:14, Victor Medina w
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 shou
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,
