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

DOC: make a warning for recidive jail to increase dbpurgeage (Closes #964)

pull/997/head
Yaroslav Halchenko 2015-03-21 20:50:03 -04:00
parent 938e6343ea
commit 320a28a4a4
2 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
ChangeLog
View File

@ -77,6 +77,7 @@ ver. 0.9.2 (2014/XX/XXX) - wanna-be-released
* Conditionally log Ignore IP with reason (dns, ip, command). Closes gh-916 * Conditionally log Ignore IP with reason (dns, ip, command). Closes gh-916
* Absorbed DNSUtils.cidr into addr2bin in filter.py, added unittests * Absorbed DNSUtils.cidr into addr2bin in filter.py, added unittests
* Added syslogsocket configuration to fail2ban.conf * Added syslogsocket configuration to fail2ban.conf
* Note in the jail.conf for the recidive jail to increase dbpurgeage (gh-964)
ver. 0.9.1 (2014/10/29) - better, faster, stronger ver. 0.9.1 (2014/10/29) - better, faster, stronger

6
config/jail.conf
View File

@ -669,10 +669,12 @@ maxretry = 5
# Jail for more extended banning of persistent abusers # Jail for more extended banning of persistent abusers
# !!! WARNING !!! # !!! WARNINGS !!!
# Make sure that your loglevel specified in fail2ban.conf/.local # 1. Make sure that your loglevel specified in fail2ban.conf/.local
# is not at DEBUG level -- which might then cause fail2ban to fall into # is not at DEBUG level -- which might then cause fail2ban to fall into
# an infinite loop constantly feeding itself with non-informative lines # an infinite loop constantly feeding itself with non-informative lines
# 2. Increase dbpurgeage defined in fail2ban.conf to e.g. 648000 (7.5 days)
# to maintain entries for failed logins for sufficient amount of time
[recidive] [recidive]
logpath = /var/log/fail2ban.log logpath = /var/log/fail2ban.log