MYSQL 新版出现" Client does not support authentication protocol requested by server; consider..

client|mysql|request|server

MYSQL 帮助:A.2.3 Client does not support authentication protocol
MySQL 4.1 and up uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older clients. If you upgrade the server to 4.1, attempts to connect to it with an older client may fail with the following message:

shell> mysqlClient does not support authentication protocol requestedby server; consider upgrading MySQL client

To solve this problem, you should use one of the following approaches:
Upgrade all client programs to use a 4.1.1 or newer client library. When connecting to the server with a pre-4.1 client program, use an account that still has a pre-4.1-style password. Reset the password to pre-4.1 style for each user that needs to use a pre-4.1 client program. This can be done using the SET PASSWORD statement and the OLD_PASSWORD() function:
mysql> SET PASSWORD FOR -> 'some_user'@'some_host' = OLD_PASSWORD('newpwd');
Alternatively, use UPDATE and FLUSH PRIVILEGES:
mysql> UPDATE mysql.user SET Password = OLD_PASSWORD('newpwd') -> WHERE Host = 'some_host' AND User = 'some_user';mysql> FLUSH PRIVILEGES;
Substitute the password you want to use for ``newpwd'' in the preceding examples. MySQL cannot tell you what the original password was, so you'll need to pick a new one. Tell the server to use the older password hashing algorithm: Start mysqld with the --old-passwords option. Assign an old-format password to each account that has had its password updated to the longer 4.1 format. You can identify these accounts with the following query:
mysql> SELECT Host, User, Password FROM mysql.user -> WHERE LENGTH(Password) > 16;
For each account record displayed by the query, use the Host and User values and assign a password using the OLD_PASSWORD() function and either SET PASSWORD or UPDATE, as described earlier.
For additional background on password hashing and authentication, see section 5.5.9 Password Hashing in MySQL 4.1.

例子:
SET PASSWORD FOR 用户名@localhost = OLD_PASSWORD('密码');

时间: 2024-09-17 03:50:32

MYSQL 新版出现" Client does not support authentication protocol requested by server; consider..的相关文章

MYSQL出现" Client does not support authentication "的解决方法_Mysql

MYSQL 帮助: A.2.3 Client does not support authentication protocol MySQL 4.1 and up uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older clients. If you upgrade the server to 4.1, attempts to

在linux中开发一个OPC Client 如何才能与windows平台的OPC Server通讯?

问题描述 在linux中开发一个OPC Client 如何才能与windows平台的OPC Server通讯? 如题,在linux中开发一个OPC Client 如何才能与windows平台的OPC Server(是其他厂家的,拿不到源代码)通讯?希望我的问题已经描述清楚了,请各位高手解答:如有赐教请联系qq:743218205,长期有效: 解决方案 OPC UA? 能满足需求吗,是不是取决于外面windows的OPC 服务器属性

Discuz论坛2.5 升级到PHP MySQL新版遇到的问题

1 中文问题,在使用MySQL实例配置工具的使用,将使用的字符集设置为GBK,而不要设置为UTF-82 MySQL安装后密码无法访问问题:mysql> SET PASSWORD FOR -> 'some_user'@'some_host' = OLD_PASSWORD('newpwd');3 PHP有Warning在php.ini里面找到bug_combat_warning = 1 两行,1 改成 04 MySQL 对SQL插入实行更强的格式检查.所以如果某个列是整数,就不能使用''来插入.因

从4.0到5.1 为什么MySQL却被冠名"玩具数据库"

  MySQL从开发人员手中的"玩具"变为如今的"世界上最流行的开源数据库",其中的过程伴随着产品版本升级,以及一些新功能(特别是企业数据库功能)的增加.现在,随着MySQL 5.0被完美地开发出来,已经很少有人将MySQL称为"玩具数据库"了.MySQL的丰富功能满足了许多用户的需求,Oracle最近的动作表明了他们对待MySQL非常重视--Oracle曾几次三番的表示有意收购MySQL. MySQL的产品路线图 让我们先从MySQL的较有影响

tomcat链接mysql时超时报错java.io.EOFException: Can not read response from server. Expected to read 4 bytes,

需要在配置文件里加上下面就ok了 <property name="minEvictableIdleTimeMillis" value="1800000″ /> <property name="numTestsPerEvictionRun" value="3″ /> <property name="testOnBorrow" value="true" /> <prop

连接远端数据库失败

问题描述 development: adapter: mysql encoding: utf8 database: name username: user password: 123456 host: 10.20.128.152这样配置数据库来访问内网其他机器的数据库!报错!Mysql::Error (Client does not support authentication protocol requested by server; consider upgrading MySQL clie

Mysql 4.1 Windows 下升级问题

mysql|window|问题 使用PHPMYADMIN时报错:Client does not support authentication protocol requestedby server; consider upgrading MySQL client 官方的说法是 MySQL 4.1 and up uses an authentication protocol based on a password hashing algorithm that is incompatible wit

MySQL常见错误提示及解决方法

130 :文件格式不正确.(还不是很清楚错误的状况) 145 :文件无法打开. 1005:创建表失败. 1006:创建数据库失败. 1007:数据库已存在,创建数据库失败. 1008:数据库不存在,删除数据库失败. 1009:不能删除数据库文件导致删除数据库失败. 1010:不能删除数据目录导致删除数据库失败. 1011:删除数据库文件失败. 1012:不能读取系统表中的记录. 1016:文件无法打开,使用后台修复或者使用 phpmyadmin 进行修复. Quote: 开始=>所有程序=>附

Windows 2000/XP/2003 下 IIS+PHP+MySQL+Zend Optimizer+GD库+phpMyAdmin安装配置

iis|mysql|window 一.软件准备:以下均为截止2005-4-20的最新正式版本PHP(5.1.2):http://www.php.net MySQL(5.0.19):http://www.mysql.com Zend Optimizer(2.6.2):http://www.zend.com phpMyAdmin(2.8.0.2):http://www.phpmyadmin.net 假设 C:\ 为你现在所使用操作系统的系统盘,如果你目前操作系统不是安装在 C:\ ,请自行修改. 二