- Page 1: Log
- Page 2: Save & Reload
- Page 3: Convenience
- Page 4: Policy
- Page 5: Encryption/Decryption Privilege
- Page 6: Access Control
- Page 7: Column Encryption Settings
Log
By setting log flags, it is determined what kind of logs will be recorded. You can check the logs in $DAMO_INST_HOME/log.
- SET LOG FLAG <deny log>”<access log>”<query log>
- <deny log>: Records log of access deny.(0: disable, 1:enable)
- <access log>: Records log of number of accesses, encryptions and decryptions for each column.(0: disable, 1:enable)
- <query log>: Record log of queries.(0: disable, 1:enable)
- SET LOG FLAG <deny log>”<access log>”<query log>
- <deny log>: Records log of access deny.(0: disable, 1:enable)
- <access log>: Records log of number of accesses, encryptions and decryptions for each column.(0: disable, 1:enable)
- <query log>: Record log of queries.(0: disable, 1:enable)
#fancy-title-673edf2f736b6 a{ color: #5b5b5b; }
Log files can be modified by someone who is not actually an administrator. Therefore, D’Amo for MySQL provides log verifying function by comparing log files’ hash values.
- VERIFY LOGFILE AGENT <Date>
- VERIFY LOGFILE CLI <Date>
- VERIFY LOGFILE KEYSERVER <Date>
- <Date>: The date of log file(policy.log) to check.(ex: year//month//day 19000101)
- VERIFY LOGFILE AGENT <Date>
- VERIFY LOGFILE CLI <Date>
- VERIFY LOGFILE KEYSERVER <Date>
- <Date>: The date of log file(policy.log) to check.(ex: year//month//day 19000101)
#fancy-title-673edf2f73b2c a{ color: #5b5b5b; }
#icon-font-673edf2f73d7a i { background-color:; color:#000000; border-color:; } #icon-font-673edf2f73d7a i:hover { background-color:; color:rgba(0,0,0,0.51); border-color:; }
Continue: Save & Reload