Bug #71573 mysqldump needs support for --skip-secure-auth
Submitted: 3 Feb 2014 23:12 Modified: 6 Feb 2014 7:00
Reporter: Todd Farmer (OCA) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:5.6.17 OS:Any
Assigned to: CPU Architecture:Any

[3 Feb 2014 23:12] Todd Farmer 
Description:
mysql supports --skip-secure-auth for use cases where a connection needs to be established using an account with pre-MySQL 4.1 password hash.  This same option is not supported for mysqldump:

D:\mysql-5.6.17-win32>bin\mysqldump --skip-secure-auth
mysqldump: unknown option '--skip-secure-auth'

D:\mysql-5.6.17-win32>bin\mysql --skip-secure-auth
Welcome to the MySQL monitor.  Commands end with ; or \g.

The consequence of this is that one cannot perform logical backups using mysqldump with an account using a pre-4.1 password hash.  The workaround is to use mysqldump from an earlier (pre-5.6.7) package.

How to repeat:
Try to use mysqldump --skip-secure-auth

Suggested fix:
Enable --skip-secure-auth flag for mysqldump
[6 Feb 2014 7:00] Anirudh Mangipudi 
This bug has been marked as duplicate of Bug#69051.
The above bug Bug#69051 has already been fixed.