Re: What changed in 4.1.7 to break DBD::Mysql
On Mon, 15 Nov 2004, Patrick Galbraith wrote: William, I'm not sure about this, because it involves windows/active state, and those ppm packages used for active state perl are pre-compiled to run. I'll talk to the current maintainer about this and see if he knows about how active state packages their DBD ppm, or if he's heard of this issue (I haven't before) Interesting. When this comes up on the linux/bsd/unix side of things, I just tell people to either recompile against the latest mysql client libraries, or set the mysql server to accept the older passwords. But now with active state, it probably gets a little more complicated. My guess is that active state is packaging DBD::mysql with an older version of the mysql libraries, and I don't know if the new client libraries will talk to older versions of MySQL (Can anyone confirm this)?, but if it is the case that the newer mysql client libraries can't talk to the older versions of mysql, then active state would have to release two version of DBD::mysql, one compiled to talk 4.1.7 and one to talk to everthing else. Or activestate just says that you have to use the old passwords with 4.1.7 (Oh, and what about the shutdown changes?) Rudy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What changed in 4.1.7 to break DBD::Mysql
Rudy Lippan wrote: On Mon, 15 Nov 2004, Patrick Galbraith wrote: William, I'm not sure about this, because it involves windows/active state, and those ppm packages used for active state perl are pre-compiled to run. I'll talk to the current maintainer about this and see if he knows about how active state packages their DBD ppm, or if he's heard of this issue (I haven't before) Interesting. When this comes up on the linux/bsd/unix side of things, I just tell people to either recompile against the latest mysql client libraries, or set the mysql server to accept the older passwords. But now with active state, it probably gets a little more complicated. My guess is that active state is packaging DBD::mysql with an older version of the mysql libraries, and I don't know if the new client libraries will talk to older versions of MySQL (Can anyone confirm this)?, but if it is the case that the newer mysql client libraries can't talk to the older versions of mysql, then active state would have to release two version of DBD::mysql, one compiled to talk 4.1.7 and one to talk to everthing else. Or activestate just says that you have to use the old passwords with 4.1.7 (Oh, and what about the shutdown changes?) Rudy New clients can talk to old servers. This is documented in the manual http://dev.mysql.com/doc/mysql/en/Password_hashing.html. Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What changed in 4.1.7 to break DBD::Mysql
Michael Stassen said: Rudy Lippan wrote: On Mon, 15 Nov 2004, Patrick Galbraith wrote: William, I'm not sure about this, because it involves windows/active state, and those ppm packages used for active state perl are pre-compiled to run. I'll talk to the current maintainer about this and see if he knows about how active state packages their DBD ppm, or if he's heard of this issue (I haven't before) Interesting. When this comes up on the linux/bsd/unix side of things, I just tell people to either recompile against the latest mysql client libraries, or set the mysql server to accept the older passwords. But now with active state, it probably gets a little more complicated. My guess is that active state is packaging DBD::mysql with an older version of the mysql libraries, and I don't know if the new client libraries will talk to older versions of MySQL (Can anyone confirm this)?, but if it is the case that the newer mysql client libraries can't talk to the older versions of mysql, then active state would have to release two version of DBD::mysql, one compiled to talk 4.1.7 and one to talk to everthing else. Or activestate just says that you have to use the old passwords with 4.1.7 (Oh, and what about the shutdown changes?) Rudy New clients can talk to old servers. This is documented in the manual http://dev.mysql.com/doc/mysql/en/Password_hashing.html. Michael Yes I know NOW. Its a problem with DBD being an OLD client. I also asked the question from the other direction on the DBI maillist and I don't know if the DBD::mysql maintainer was aware of the implications. He was focusing on stored procedures (a 5.x option I thougth). A warning should go into the Perl interface section of the manual (~~Temporarily you will have to use OLD_PASSWORD until DBD::mysql is updated~~ or some such). Once you know what the problem is you can look in the correct section of the manual, but until then I didn't know where to look. But it was Monday. Bill -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What changed in 4.1.7 to break DBD::Mysql
William R. Mussatto wrote: I've been googling for 1/2 hr w/o any answers. sorry if I've missed the obvious. Problem. Fresh install of mysql 4.7.1, AS perl 5.8 DBI and DBD-Mysql via ppm. Client does not support authnticaiton protocol What version of MySQL were you using previously? If it was 4.1.0 or earlier, then this might be useful reading: http://dev.mysql.com/doc/mysql/en/Password_hashing.html -- Keith Ivey [EMAIL PROTECTED] Washington, DC -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What changed in 4.1.7 to break DBD::Mysql
Keith Ivey said:
William R. Mussatto wrote:
I've been googling for 1/2 hr w/o any answers. sorry if I've missed
the obvious.
Problem. Fresh install of mysql 4.7.1, AS perl 5.8
DBI and DBD-Mysql via ppm.
Client does not support authnticaiton protocol
What version of MySQL were you using previously? If it was 4.1.0 or
earlier, then this
might be useful reading:
http://dev.mysql.com/doc/mysql/en/Password_hashing.html
--
Keith Ivey [EMAIL PROTECTED]
Washington, DC
Thanks, I'll check it out. I did the development under linux using
3.23.xx and perl 5.6 Basically debian stable.
From the article it looks like I'll have to fall back to a 4.0 version.
I was hoping, but using a clean install on the windows box to avoid these
issues.
I'll try SET PASSWORD FOR 'some_user'@'some_host' = OLD_PASSWORD('mypass');
Thanks that worked, now to see what happends when I try w/connector/J
--
William R. Mussatto, Senior Systems Engineer
Ph. 909-920-9154 ext. 27
FAX. 909-608-7061
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What changed in 4.1.7 to break DBD::Mysql
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William R. Mussatto wrote:
Keith Ivey said:
William R. Mussatto wrote:
I've been googling for 1/2 hr w/o any answers. sorry if I've missed
the obvious.
Problem. Fresh install of mysql 4.7.1, AS perl 5.8
DBI and DBD-Mysql via ppm.
Client does not support authnticaiton protocol
What version of MySQL were you using previously? If it was 4.1.0 or
earlier, then this
might be useful reading:
http://dev.mysql.com/doc/mysql/en/Password_hashing.html
--
Keith Ivey [EMAIL PROTECTED]
Washington, DC
Thanks, I'll check it out. I did the development under linux using
3.23.xx and perl 5.6 Basically debian stable.
From the article it looks like I'll have to fall back to a 4.0 version.
I was hoping, but using a clean install on the windows box to avoid these
issues.
I'll try SET PASSWORD FOR 'some_user'@'some_host' = OLD_PASSWORD('mypass');
William,
You'll need a copy of DBD::MySQL that's linked with libmysql from 4.1 to
get around this issue (and use the new server-side prepared statements
as well). Patrick Galbraith (a MySQL engineer) has pushed the required
changes into the CVS repo of DBD::MySQL, however that hasn't been
released yet as a binary by the DBD::MySQL maintainer (DBD::MySQL
version 2.9015)
Thanks that worked, now to see what happends when I try w/connector/J
As long as you're using a recent version of Connector/J (3.0.15 or
3.1.4), it'll work fine.
Regards,
-Mark
- --
Mark Matthews
MySQL AB, Software Development Manager - Client Connectivity
Office: +1 708 332 0507
www.mysql.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBmUi5tvXNTca6JD8RAllHAJ4060+3153gCOUo5IKBthDEHsUN2wCfYeNc
tkoDjKqS0DBxz7mE7ZWIqG8=
=hqLF
-END PGP SIGNATURE-
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What changed in 4.1.7 to break DBD::Mysql
Mark Matthews said:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William R. Mussatto wrote:
Keith Ivey said:
William R. Mussatto wrote:
I've been googling for 1/2 hr w/o any answers. sorry if I've missed
the obvious.
Problem. Fresh install of mysql 4.7.1, AS perl 5.8
DBI and DBD-Mysql via ppm.
Client does not support authnticaiton protocol
What version of MySQL were you using previously? If it was 4.1.0 or
earlier, then this
might be useful reading:
http://dev.mysql.com/doc/mysql/en/Password_hashing.html
--
Keith Ivey [EMAIL PROTECTED]
Washington, DC
Thanks, I'll check it out. I did the development under linux using
3.23.xx and perl 5.6 Basically debian stable.
From the article it looks like I'll have to fall back to a 4.0
version.
I was hoping, but using a clean install on the windows box to avoid
these issues.
I'll try SET PASSWORD FOR 'some_user'@'some_host' =
OLD_PASSWORD('mypass');
William,
You'll need a copy of DBD::MySQL that's linked with libmysql from 4.1 to
get around this issue (and use the new server-side prepared statements
as well). Patrick Galbraith (a MySQL engineer) has pushed the required
changes into the CVS repo of DBD::MySQL, however that hasn't been
released yet as a binary by the DBD::MySQL maintainer (DBD::MySQL
version 2.9015)
Thanks that worked, now to see what happends when I try w/connector/J
As long as you're using a recent version of Connector/J (3.0.15 or
3.1.4), it'll work fine.
Regards,
-Mark
- --
Mark Matthews
MySQL AB, Software Development Manager - Client Connectivity
Office: +1 708 332 0507
www.mysql.com
Thanks, I figured I just hit it at the wrong time (4.1.7 out but DBD not
yet updated). the connector/j just came down from mysql.com so it should
be current. I do most of my production work on debian linux but wanted to
give this client the current stuff.
--
William R. Mussatto, Senior Systems Engineer
Ph. 909-920-9154 ext. 27
FAX. 909-608-7061
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What changed in 4.1.7 to break DBD::Mysql
Patrick Galbraith said:
William,
What was the error that you had specifically? Did you use a precompiled
version of DBD::mysql like a RPM, or did you build it yourself? I don't
know if this is a DBD version issue that you are experiencing, because
nothing was changed in authentication protocol. The main thing that
I've coded into the newer version of DBD::mysql is support for prepared
statements.
regards,
Patrick
The DBD::mysql is from Active State's repository via the ppm auto install
process. The version they supply supports only the older short passwords.
Since I missed the change in 4.1.x to longer passwords I was unable to
connect to the newly installed mysql using the DBI interface. I'm not
sure of clean way other than what I did (force the use of old_password's.
I have other boxes which run older mysql which have to support the old
interfaces. The only think I can think to do (assuming you can't ask
which version is supported) is to try the long and then the short version
of the passwords, or to allow the default behavior of the DBI- connect
function to be altered by a parameter.
On Nov 15, 2004, at 5:14 PM, William R. Mussatto wrote:
Mark Matthews said:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William R. Mussatto wrote:
Keith Ivey said:
William R. Mussatto wrote:
I've been googling for 1/2 hr w/o any answers. sorry if I've
missed
the obvious.
Problem. Fresh install of mysql 4.7.1, AS perl 5.8
DBI and DBD-Mysql via ppm.
Client does not support authnticaiton protocol
What version of MySQL were you using previously? If it was 4.1.0
or earlier, then this
might be useful reading:
http://dev.mysql.com/doc/mysql/en/Password_hashing.html
--
Keith Ivey [EMAIL PROTECTED]
Washington, DC
Thanks, I'll check it out. I did the development under linux using
3.23.xx and perl 5.6 Basically debian stable.
From the article it looks like I'll have to fall back to a 4.0
version.
I was hoping, but using a clean install on the windows box to avoid
these issues.
I'll try SET PASSWORD FOR 'some_user'@'some_host' =
OLD_PASSWORD('mypass');
William,
You'll need a copy of DBD::MySQL that's linked with libmysql from 4.1
to
get around this issue (and use the new server-side prepared
statements as well). Patrick Galbraith (a MySQL engineer) has pushed
the required changes into the CVS repo of DBD::MySQL, however that
hasn't been released yet as a binary by the DBD::MySQL maintainer
(DBD::MySQL version 2.9015)
Thanks that worked, now to see what happends when I try
w/connector/J
As long as you're using a recent version of Connector/J (3.0.15 or
3.1.4), it'll work fine.
Regards,
-Mark
- --
Mark Matthews
MySQL AB, Software Development Manager - Client Connectivity
Office: +1 708 332 0507
www.mysql.com
Thanks, I figured I just hit it at the wrong time (4.1.7 out but DBD
not
yet updated). the connector/j just came down from mysql.com so it
should
be current. I do most of my production work on debian linux but
wanted to
give this client the current stuff.
--
William R. Mussatto, Senior Systems Engineer
Ph. 909-920-9154 ext. 27
FAX. 909-608-7061
Patrick Galbraith Senior Software Developer
[EMAIL PROTECTED] http://www.mysql.com
Whatever action a great man performs, common men follow. Whatever
standards he sets by exemplary acts, all the world pursues --
Bhagavad Gita
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
