atmos
/
ban2fail
mirror of https://github.com/jrbrtsn/ban2fail
1
1
Fork 0
Code Issues Releases Wiki Activity

Edits.

This commit is contained in:
john 2019-12-07 08:55:08 -05:00
parent 72df5dfc03
commit 44535df94c
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -7,7 +7,8 @@ reporting, and iptables filtering. As the name implies, *ban2fail* was
inspired by the popular *fail2ban* project (http://fail2ban.org). The main
technical advantages *ban2fail* provides over *fail2ban* are:
+ All relevant logfiles on disk are scanned, not just the current log files.
+ By design all relevant logfiles on disk are scanned, not just the current
log files.
+ A unique and transparent caching scheme is employed to make this process at
least 100x as fast as doing the same thing with, say, *grep*.
@ -30,6 +31,9 @@ lookups.
+ Efficient enough to run every 0.4 seconds without monopolizing a CPU core on a
modest server.
+ In the case of a reboot or after iptables filters get flushed, blocking rules
will be instantaneously generated from entire log file histories (long memory).
*ban2fail* started with a few hours of frenzied C hacking after my mail server
was exploited to deliver spam for others who had cracked a user's SMTP send