MySQL Bugs: #68599: Warning issued about master.info when using master-info-repository=table

Bug #68599	Warning issued about master.info when using master-info-repository=table
Submitted:	7 Mar 2013 15:51	Modified:	28 Jun 2013 14:29
Reporter:	Kolbe Kegel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.6.10	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
The CHANGE MASTER TO statement issues a warning about master.info even when the server is running with master-info-repository=table:

Storing MySQL user name or password information in the master.info repository is not secure and is therefore not recommended. Please see the MySQL Manual for more about this issue and possible alternatives.

How to repeat:
set global master_info_repository='table';
change master to master_host='127.0.0.1', master_port=4001, master_user='root', master_auto_position=1;
show warnings\G

box2> set global master_info_repository='table';
Query OK, 0 rows affected (0.00 sec)

box2> change master to master_host='127.0.0.1', master_port=4001, master_user='root', master_auto_position=1;                                                 Query OK, 0 rows affected, 2 warnings (0.06 sec)

box2> show warnings\G
*************************** 1. row ***************************
  Level: Note
   Code: 1759
Message: Sending passwords in plain text without SSL/TLS is extremely insecure.
*************************** 2. row ***************************
  Level: Note
   Code: 1760
Message: Storing MySQL user name or password information in the master.info repository is not secure and is therefore not recommended. Please see the MySQL Manual for more about this issue and possible alternatives.
2 rows in set (0.01 sec)

This also happens when the server is started with master-info-repository=table.

Suggested fix:
Do not issue this warning if the server is running with master-info-repository=table.

I think that in fact this issue is just basically written nonsensically. It needs to be rewritten entirely, and the context in which it is issued should remain the same: See bug #68602

Someone else can decide whether I'm right about that.

Thank you for the bug report. Verified as described on recent 5.6.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

Fixed in 5.6+. Documented in the 5.6.13 and 5.7.2 changelogs as follows:

        The warning issued when specifying MASTER_USER or
        MASTER_PASSWORD with CHANGE MASTER TO was unclear for a number
        of reasons, and has been changed to read, «Storing MySQL user
        name or password information in the master info repository is
        not secure and is therefore not recommended. Please consider
        using the USER and PASSWORD connection options for START SLAVE;
        see 'START SLAVE Syntax' in the MySQL Manual for more
        information.»

Closed.

Note that this also fixes BUG#68602.