fail2ban_0.8.6-3~bpo60+1_i386.changes is NEW
(new) fail2ban_0.8.6-3~bpo60+1.diff.gz optional net
(new) fail2ban_0.8.6-3~bpo60+1.dsc optional net
(new) fail2ban_0.8.6-3~bpo60+1_all.deb optional net
ban hosts that cause multiple authentication errors
Fail2ban monitors log files (e.g. /var/log/auth.log,
/var/log/apache/access.log) and temporarily or persistently bans
failure-prone addresses by updating existing firewall rules. Fail2ban allows
easy specification of different actions to be taken such as to ban an
IP using iptables or hostsdeny rules, or simply to send a
notification email.
.
By default, it comes with filter expressions for various services
(sshd, apache, qmail, proftpd, sasl etc.) but configuration can be
easily extended for monitoring any other text file. All filters and
actions are given in the config files, thus fail2ban can be adopted
to be used with a variety of files and firewalls.
(new) fail2ban_0.8.6.orig.tar.gz optional net
Changes: fail2ban (0.8.6-3~bpo60+1) squeeze-backports; urgency=low
.
* Rebuild for squeeze-backports.
.
fail2ban (0.8.6-3) unstable; urgency=low
.
* Added dovecot section to Debian's jail.conf. Thanks to Laurent
Léonard (Closes: #655182)
* init.d script now returns non-0 exit codes upon status command
with not running / failed to connect server. Thanks to
Glenn Aaldering for the patch
.
fail2ban (0.8.6-2) unstable; urgency=low
.
* Added pure-ftpd section to Debian's jail.conf. Thanks to Laurent
Léonard (Closes: #654412)
* Enhancement: action to use /proc/net/xt_recent and run f2b as a normal
user. Many many thanks to Zbyszek Szmek (Closes: #602016)
.
fail2ban (0.8.6-1) unstable; urgency=low
.
* [1efe1bc] Fresh upstream release (Closes: #648324)
* Boosted policy compliance to 3.9.2 -- no changes
* Adjusted debian/watch to fetch tarballs from github
.
fail2ban (0.8.5-2) unstable; urgency=low
.
* [5242e73] BF: (cherry-picked from upstream, DEP-3 yet TODO) Lock
server's executeCmd to prevent racing among iptables calls (Closes:
#554162) Many kudos go to Michael Saavedra for the patch
.
fail2ban (0.8.5-1) unstable; urgency=low
.
* [de95777] Fresh upstream release FAIL2BAN-0_8_5:
- [00e1827] BF: use addfailregex instead of failregex while processing
per-jail "failregex" parameter (Closes: #635830) (LP: #635036)
Thanks Marat Khayrullin for the patch and Daniel T Chen for forwarding to
Debian.
* [1cbdafc] Set backend to auto and recommends python-gamin (Closes: #524425)
* [ef449f4] Added a note on diverting logrotate configuration for custom
logtarget=SYSLOG (Closes: #631917). Thanks Kenyon Ralph for report
.
fail2ban (0.8.4+svn20110323-1) unstable; urgency=low
.
* Fresh upstream snapshot which absorbed some of the patches from Debian
and
- [c6d64e9] debug entry for lines ignored due to falling below
findtime (v2)
- [fc20f12] Tai64N stores time in GMT, we need to convert to
local time before returning
- [b0331bb] default ignoreip to ignore entire loopback zone (/8)
(Closes: #598200)
- [b9f15f6] ENH: dovecot filter
- [69165b1] ENH: add <chain> to action.d/iptables*. Thanks
Matthijs Kooijman
- [8330a20] ENH: make filter.d/apache-overflows.conf catch more
(Closes: #574182)
- [66cc6cb] BF: allow space in the trailing of failregex for sasl.conf
(Closes: #573314)
- [2714019] ENH: dropbear filter (Closes: #546913)
- [ea7d352] BF: Use /var/run/fail2ban instead of /tmp for temp files in
actions (Closes: #544232)
* debian/jail.conf:
- [bc8e22d] spellcheck (Closes: #598206). Thanks Christoph Anton Mitterer
- [d7f3e23] adjusted description for sasl jail (Closes: #615952)
- [92fb484] debian/jail.conf: closing " for protocol specification
- [f828c31] debian/jail.conf: got 'chain' parameter to be specified for
iptables actions (Closes: #515599)
* debian/control:
- [858af30] slight rewordings of the long description (Closes: #588176)
- [167dfd4] Boosted policy compliance version to 3.9.1 (no changes seems
to be due)
* [4e1e845] debian/copyright: updated copyright years
Override entries for your package:
Announcing to debian-backports-changes@lists.debian.org
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override file about once a week.
You may have gotten the distribution wrong. You'll get warnings above
if files already exist in other distributions.
Reply to: