12:28 ~ / Mysql_history and security | |
| Typically, security is inversely proportional to convenience. To preserve the history of commands that can be navigated in the CLI, - very convenient. So does, for example, bash. So doing, and MySQL, and carefully line by writing the command in ~ /. Mysql_history in plain text (including passwords). To reduce or entirely avoid the risk of leakage is possible if (the more acceptable, in my opinion, the way to a less valid):
From the perspective of the DBMS is not a security issue, since in the history of queries can be much more valuable information than passwords (billing information, for example), so developers do not take care of such exceptions on the level of logging history command. Actually what touched upon this theme. What are some more options? Bonus track. Referring to the issue of safety MySQL, I want to note that the observed data are often the root account in a backup script using mysqldump. A very common mistake, and yet not too difficult to create a special user to unload a pair of bases commands: GRANT SELECT, LOCK TABLES ON .* TO <user-dumper> @ localhost IDENTIFIED BY '<dumper-password> '; FLUSH PRIVILEGES; | |
|
| |
| Total comments: 0 | |