Bug #77550 MySQL Utilities Usage of .mylogin.cnf broken as of MySQL Server 5.6.25
Submitted: 29 Jun 2015 21:00 Modified: 2 Feb 2016 2:01
Reporter: Jim Parks Email Updates:
Status: Closed Impact on me:
Category:MySQL Utilities Severity:S2 (Serious)
Version: OS:Any
Assigned to: CPU Architecture:Any

[29 Jun 2015 21:00] Jim Parks
MySQL Utilities can not use .mylogin.cnf as of MySQL Server 5.6.25.

Prior to 5.6.25, my_print_defaults returned an unencrypted password from .mylogin.cnf, which was used by utilities.  As of 5.6.25, passwords are returned as "****" and this breaks utilities.

How to repeat:
Install MySQL 5.6.25 and attempt to use login paths as values for master, server, or rpl-user.

Leave 5.6.25 in place and replace /usr/bin/my_print_defaults with the version from 5.6.24, and utilities work again.

Suggested fix:
Make utilities work the same way other clients do when using .mylogin.cnf for login paths.
[2 Feb 2016 2:01] Philip Olson
Fixed as of the upcoming MySQL Utilities 1.6.3 release, and here's the
changelog entry:

The MySQL utilities did not function with .mylogin.cnf as of MySQL Server

Thank you for the bug report.