* Wim Bertels <[EMAIL PROTECTED]> wrote: <snip> > since brute force attacks are quit traceable (targetting one and the > same user eg..), > one could a script to check: > - the percentage of failed logins/user, depending on the percentage (eg > 75% or more failed, this should be configurable), these events should be > reporteg in security.log file under the postgres log directory, or > mailed to user (inetd...) > - if there are more than eg 10 (this should be configurable) failed > consecutive logins/user, this should again be reported.
BTW: is it possible to do this directly in the database - by rules and triggers on the appropriate system tables ? cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] --------------------------------------------------------------------- Realtime Forex/Stock Exchange trading powered by postgresSQL :)) http://www.fxignal.net/ --------------------------------------------------------------------- ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
