How to securely process passwords in MySQL5.6

There are a lot of changes to the password in MySQL5.6, including: Brand new password hashing algorithm (SHA-256 ). for password obfuscation in the mylogin file, you can choose to store the server load balancer node password in the database table. you can specify the password in startserver load balancer, but there is no article to describe the password... "> <LINKhref =" http://www.php100.com//s

There are many changes to the password in MySQL 5.6, including:

• New cryptographic hashing algorithm (SHA-256)
• . Mylogin file obfuscation of password
• You can choose to store the Slave node password in the database table
• You can specify a password in start slave.

However, there is no article about this.

This article describes how to automatically hide passwords in your log files in MySQL 5.6.

MySQL 5.6 will automatically hide the password information in the log. This is not just obfuscation, and then stores the unidirectional hash value in the log file. You can disable password hiding for log files by setting log-raw = OFF. The log-raw setting only affects general logs, while the password is hidden in slow query logs and binary logs.

In MySQL 5.5, this requires manual processing when the hash is stored in the variable for the first time. However, this is useless in most scenarios.

However, according to the mysql command manual, the mysql command does not record the statement that matches "* IDENTIFIED *: * PASSWORD.

However, do not forget to verify the permission protection for the MySQL server and client log files, including other files such as master.info. In addition, if you need to use the MySQL privileged system for protection when storing Slave node creden in the database, if master.info enables someone to have too many Database permissions, you can also use load data infile to LOAD the content.

Of course, there are still some improvements:

This is even better if we can easily enable secure connections. MySQL and many other applications use TLS, but there are some performance problems and it is not easy to set. In addition, MySQL is not secure by default and is simple.

Therefore, the security of MySQL 5.6 is improved without any configuration.