MySQL-5.6.11-1を使ã£ã¦ã„ã‚‹å ´åˆã«ã¯MySQL-5.6.11-2ã¸ã‚¢ãƒƒãƒ—デートã—ã¾ã—ょã†ã€‚
ç¾è±¡
PHPãªã©ã‹ã‚‰æŽ¥ç¶šã—ãŸå ´åˆã«ã€ä»¥ä¸‹ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¦æŽ¥ç¶šãŒå‡ºæ¥ãªã„ã¨ã„ã†ã‚‚ã®ã§ã™ã€‚
ERROR 2049 (HY000): Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)
対象ユーザ
Version: 5.6.11 Release: 1.el6 ã®MySQLを使ã£ã¦ã„ã‚‹æ–¹ãŒå¯¾è±¡ã§ã™ã€‚
例ãˆã°ã€ä»¥ä¸‹ã®çµæžœã§ã‚れã°ã‚¢ãƒƒãƒ—デート対象ã§ã™ã€‚
$ rpm -qa | grep ^MySQL MySQL-server-5.6.11-1.el6.x86_64 MySQL-shared-compat-5.6.11-1.el6.x86_64 MySQL-shared-5.6.11-1.el6.x86_64 MySQL-devel-5.6.11-1.el6.x86_64 MySQL-client-5.6.11-1.el6.x86_64
è©³ç´°æƒ…å ±
http://bugs.mysql.com/bug.php?id=69027
å‚考文献
http://mysqlha.blogspot.jp/2013/04/good-news-mysql-5611-is-here.html より引用
FYI: seems there's a bug in the way MySQL 5.6.11 handles pre-4.1.1 password hashes and mysql_init() always throws CR_SECURE_AUTH error, see http://bugs.mysql.com/bug.php?id=69027
https://groups.google.com/forum/?fromgroups=#!topic/powerstack-testing/4jDtJo9jwIs より引用
WARN: there's a bug in the way MySQL 5.6.11 handles "pre-4.1.1" format passwords, the server always returns CR_SECURE_AUTH error although it's started with secure_auth [1] mode disabled (skip-secure-auth option). I have just commited a patch [2] that backports mysql_init() from MySQL 5.6.10 and enables this feature again: http://kcy.me/jbqt So, there's no reason to hold MySQL 5.6.11 packages any further, tomorrow I will push "mysql-5.6.11-2" packages to "stable" repository. [1]
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_secure_auth [2]
https://github.com/santisaez/powerstack/blob/master/packages/mysql/mysql-powerstack-secure_auth.patch
PlanetMySQL Voting: Vote UP / Vote DOWN