[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [php-maint] php5-mysql in backports.org linked against libmysqlclient14?



On Friday 12 January 2007 02:24, Sidney Markowitz wrote:
> I was installing this package from backports because I was given access
> to a machine with Debian sarge to use as a client for a MySQL 4.1.11
> server with a database and user already set up. Accessing that database
> requires a MySQL client library version 4.1.1 or newer, or else it
> produces the error message
>  "Client does not support authentication protocol"
> as documented in
>   http://dev.mysql.com/doc/refman/5.0/en/old-client.html
>
> I don't have ready control to change the password format on the server
> to the old style so that it will work with a 4.0.x client.
>
> I don't know how to solve the problem that this thread is addressing,
> but the solution of linking against libmysqlclient12-dev reintroduces
> one big reason for wanting to install php5-mysql in the first place.

Hi Sidney,

you are using mysql 5.x as server, right? Then you should insert the following 
into your /etc/mysql/my.cnf

[mysqld]
old_passwords = true # inserted by debconf
# Activate the above for connections from hosts running Debian Woody/Sarge!
#
# Prior to MySQL 5.0, user passwords were stored in a rather weak way. This
# has been improved with the drawback that client programs shipped with
# Debian Woody/Sarge (technically: linked against libmysqlclient.so.12 or
# earlier) cannot connect any more if either their account has either been
# created or their password has been modified using MySQL 5.0.
# See http://dev.mysql.com/doc/refman/5.0/en/old-client.html

With kind regards, Jan.
-- 
Never write mail to <waja@spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------

Attachment: pgpP_hIkNj7y8.pgp
Description: PGP signature


Reply to: