MySQL 5.6 How to change a secure handling password discussion _mysql

MySQL 5.6 will automatically hide the password information in the log. This is not just confusing, then the one-way hash value is stored in the log file. You can disable the password-hiding feature of the log file by setting Log-raw=off. Log-raw settings affect only general logs, and passwords are still hidden in slow query logs and binary logs.

In MySQL 5.5 This needs to be handled manually when the hash is first stored in a variable. But it's no use in most scenarios.
But more than that, according to the MySQL command manual, the MySQL command will not record a match to the "*identified*:* password*" statement.

Still, don't forget to check the MySQL server and client log files for permission protection, including other files such as Master.info. In addition, if you store credentials from a node in a database that need to be protected with a MySQL privileged system, you should do so if master.info makes someone have too much database permissions and can load content with the load DATA INFILE.

Of course, there is still room for improvement:
This would be better if we could easily enable secure connections. MySQL and many other applications use TLS, but there are some performance issues and it's not easy to set up. In addition MySQL defaults are unsafe, just for simplicity.
So MySQL 5.6 improves security without any configuration.