Bug #60559 auth log
Submitted: 21 Mar 2011 3:31 Modified: 21 Mar 2011 5:35
Reporter: Roberto Spadim (Basic Quality Contributor) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Logging Severity:S4 (Feature request)
Version:any OS:Any
Assigned to: CPU Architecture:Any
Tags: auth, qc

[21 Mar 2011 3:31] Roberto Spadim 
Description:
hi guys, could we implement a auth log?
for example, i must know who (ip/user/ maybe password) couldn't connect at mysql, and why (max connections, wrong password, user don't exists, host not founded, others)

it's a tool to prevent hacker attacks

How to repeat:
maybe a option

wrong-auth-log=/home/mysql/log/auth.log

Suggested fix:
no one
[21 Mar 2011 4:29] Roberto Spadim 
changed to logging category
[21 Mar 2011 5:25] Valeriy Kravchuk 
Check http://forge.mysql.com/worklog/task.php?id=1410 and http://forge.mysql.com/worklog/task.php?id=2878.
[21 Mar 2011 5:31] Roberto Spadim 
maybe put more information at WL 2878
today:
* Security Audit Report
** Security changes for specified objects 
** Security changes for specified objects in last N days 
** Security changes performed by specified users 
** Activity for which permission was denied 
** Login activity for specified users 

add:
** Login activity for wrong user/password/host

should i change this bug to closed?
[21 Mar 2011 5:35] Roberto Spadim 
about wl 1410
yes, don't put with general log, it's just for secure reasons (servers connected at internet)
a syslog interface is nice too :) good idea :)
the question here is more related about log users (programs with php+apache+syslog+linux log directory, i don't know about users with windows or others o.s.)