MySQL Bugs: #65462: Server doesn't warn about starting with --skip-secure-auth

Bug #65462	Server doesn't warn about starting with --skip-secure-auth
Submitted:	30 May 2012 14:23	Modified:	28 Jul 2012 22:44
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Options	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
MySQL 5.6.5 (and higher) should warn when started with --skip-secure-auth, but it does not:

D:\mysql-5.6.5-m8-win32>bin\mysqld --no-defaults --console --port=3307 --skip-secure-auth
120530  7:21:20 [Note] Plugin 'FEDERATED' is disabled.
120530  7:21:20 InnoDB: The InnoDB memory heap is disabled
120530  7:21:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120530  7:21:20 InnoDB: Compressed tables use zlib 1.2.3
120530  7:21:20 InnoDB: CPU does not support crc32 instructions
120530  7:21:20 InnoDB: Initializing buffer pool, size = 128.0M
120530  7:21:20 InnoDB: Completed initialization of buffer pool
120530  7:21:20 InnoDB: highest supported file format is Barracuda.
120530  7:21:20 InnoDB: 128 rollback segment(s) are active.
120530  7:21:20 InnoDB: 1.2.5 started; log sequence number 1699464
120530  7:21:20 [Note] Event Scheduler: Loaded 0 events
120530  7:21:20 [Note] bin\mysqld: ready for connections.
Version: '5.6.5-m8'  socket: ''  port: 3307  MySQL Community Server (GPL)

This seems to be the case regardless of whether --skip-secure-auth is passed as a command-line argument or specified in the configuration file:

D:\mysql-5.6.5-m8-win32>bin\mysqld --defaults-file=secure-test.ini --console --port=3307
120530  7:19:34 [Note] Plugin 'FEDERATED' is disabled.
120530  7:19:34 InnoDB: The InnoDB memory heap is disabled
120530  7:19:34 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120530  7:19:34 InnoDB: Compressed tables use zlib 1.2.3
120530  7:19:34 InnoDB: CPU does not support crc32 instructions
120530  7:19:34 InnoDB: Initializing buffer pool, size = 128.0M
120530  7:19:34 InnoDB: Completed initialization of buffer pool
120530  7:19:35 InnoDB: highest supported file format is Barracuda.
120530  7:19:35 InnoDB: 128 rollback segment(s) are active.
120530  7:19:35 InnoDB: 1.2.5 started; log sequence number 1699454
120530  7:19:36 [Note] Event Scheduler: Loaded 0 events
120530  7:19:36 [Note] bin\mysqld: ready for connections.
Version: '5.6.5-m8'  socket: ''  port: 3307  MySQL Community Server (GPL)

How to repeat:
Start 5.6.5 with --skip-secure-auth, both as command-line argument and in configuration file.

Suggested fix:
Provide warning.

Also note that there is no warning when secure_auth is disabled dynamically:

mysql> SET GLOBAL secure_auth = ON;
Query OK, 0 rows affected (0.00 sec)

(also nothing in server error log)

Noted in 5.6.7, 5.7.0 changelogs.

If the server was started with secure_auth disabled, it did not
produce a warning that this is a deprecated setting.