github
/
mysql-audit
mirror of https://github.com/mcafee-enterprise/mysql-audit
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated Configuration (markdown)

master
Guy Lichtman 2014-07-07 00:14:47 -07:00
parent c4efab9e75
commit 14c280b95a
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Configuration.md

@ -15,6 +15,8 @@ Available AUDIT Plugin system varaibles:
* **audit_record_objs**: Comma separated list of objects (tables) to log to the audit trail. Table name should be specified as: `database.table`. Wild cards are supported and it is possible to specify: `*.mytable` or `mydb.*`. * **audit_record_objs**: Comma separated list of objects (tables) to log to the audit trail. Table name should be specified as: `database.table`. Wild cards are supported and it is possible to specify: `*.mytable` or `mydb.*`.
* **audit_whitelist_users**: Comma separated list of white-listed users whose queries are not recorded. * **audit_whitelist_users**: Comma separated list of white-listed users whose queries are not recorded.
* **audit_header_msg**: Header message logging ON|OFF. Default value: ON. Introduced at version 1.0.6. * **audit_header_msg**: Header message logging ON|OFF. Default value: ON. Introduced at version 1.0.6.
* **audit_password_masking_cmds**: Comma separated list of commands for which the password masking regex will be applied. Default value includes MySQL commands that may include a password clause: CREATE_USER,GRANT,SET_OPTION,SLAVE_START,CREATE_SERVER,ALTER_SERVER,CHANGE_MASTER. Introduced at version 1.0.6.
* **audit_password_masking_regex**: PCRE complaint regular expression used for password masking. Regex will be applied only to statements with command type as specified at: `audit_password_masking_cmds`. Introduced at version 1.0.6.
**Notes:** **Notes:**
* When configuring boolean variables (enable/disable) in MySQL 5.1 via a configuration file (my.cnf) use 0/1 as values. For example: `audit_json_file=1`. There seems to be an issue with MySQL 5.1 where boolean configurations with `ON/OFF` values in my.cnf don't work. * When configuring boolean variables (enable/disable) in MySQL 5.1 via a configuration file (my.cnf) use 0/1 as values. For example: `audit_json_file=1`. There seems to be an issue with MySQL 5.1 where boolean configurations with `ON/OFF` values in my.cnf don't work.