When you connect a MySQL server, you should usually use a password. The password is not transmitted in clear text on the connection.
All other information is transmitted as text that can be read by anyone. If you're worried about this, you can use a compression protocol (MySQL3.22 and above) to make things harder. Even to make everything more secure, you should install SSH (see HTTP://WWW.CS.HUT.FI/SSH). With it, you can get an encrypted TCP/IP connection between a MySQL server and a MySQL client.
To make a MySQL system secure, you are strongly asked to consider the following recommendations:
Use passwords for all MySQL users. Remember, if Other_user does not have a password, anyone can simply log in with Mysql-u Other_user db_name as any other person. For client/server applications, it is common practice for customers to specify any user name. Before you run it, you can change the password for all users by editing the mysql_install_db script, or just the password for MySQL root, like this:
shell> mysql-u Root MySQL
mysql> UPDATE user SET Password=password (' New_password ')
WHERE user= ' root ';
mysql> FLUSH privileges;
Do not run the MySQL daemon as the root user of Unix. Mysqld can run with any user, you can also create a new UNIX user MySQL to make everything more secure. If you run mysqld as another UNIX user, you do not need to change the root user name in the user table because the MySQL user name does not matter with the UNIX username. You can edit Mysql.server startup script Mysqld as other UNIX users. Usually this is done with the SU command. For more details, see 18.8 How to run MySQL as a general user.
If you put a UNIX root user password in the Mysql.server script, make sure that the script is readable only to root.
Check that the UNIX user running mysqld is the only user who has read/write permissions in the database directory.
Do not give the process permission to all users. The output of the Mysqladmin processlist shows the currently executing query body, and if another user issues an update to the SET Password=password (' not_secure ') query, Any user who is allowed to execute that command may see it. Mysqld keeps an extra connection for users with process permissions so that a MySQL root user can log in and check, even if all of the normal connections are in use.
Do not give file permissions to all users. Any user with this permission can write a file in the file system that has the mysqld daemon privileges! To make this more secure, use SELECT ... All files generated by into outfile are readable to everyone, and you cannot overwrite files that already exist. File permissions can also be used to read any files that are accessible to UNIX users running the server. This can be abused, for example, by loading "/etc/passwd" into a database table by using load data, and then it can be read in with SELECT.
If you do not trust your DNS, you should use the IP number instead of the hostname in the authorization table. In principle, the--secure option should make the host name more secure for mysqld. In any case, you should be very careful to use a host name that contains a wildcard character
http://www.bkjia.com/PHPjc/632388.html www.bkjia.com true http://www.bkjia.com/PHPjc/632388.html techarticle When you connect a MySQL server, you should usually use a password. The password is not transmitted in clear text on the connection. All other information is transmitted as text that can be read by anyone. Like ...
