Ubuntu Archive Auto-Sync katie at jackass.ubuntu.com
Tue Oct 25 17:26:09 CDT 2005

Hash: SHA1

Origin: Debian/unstable
Format: 1.7
Date: Tue,  25 Oct 2005 21:50:49 +0100
Source: fail2ban
Binary: fail2ban
Architecture: source
Version: 0.5.4-5.14
Distribution: dapper
Urgency: low
Maintainer: Yaroslav Halchenko <debian at onerussian.com>
Changed-By: Ubuntu Archive Auto-Sync <katie at jackass.ubuntu.com>
 fail2ban   - bans IPs that cause multiple authentication errors
Closes: 323451 323543 323840 329163 329304 329722 330311 330827 331695 333056
 fail2ban (0.5.4-5.14) unstable; urgency=low
   * Added a notification regarding the importance of 0.5.4-5 change of
     failregex in the config file.
   * Adjusted address to FSF.
   * Adjusted failregex for SSH so it bans "Illegal user" entries as well, and
     restricted full failregex more to include ":" at the beginning, because
     otherwise it might not be sufficient and would revive bug 330827 (closes:
   * Adjusted failregex for SSH to accommodate recent changes in logging of
     SSH: Illegal -> Invalid. Should match both now.
   * Fixed a problem of raise AttributeError exception reported as a side
     effect of crash during parsing of the config file.
   * Introduced fwcheck option to verify consistency of the
     chains. Implemented automatic restart of fail2ban main function in
     case if check of fwban or fwban command failed (closes: #329163, #331695).
     (Introduced patch was further adjusted by upstream author).
   * Added -f command line parameter for [findtime].
   * Fixed the issue of not respecting command line parameters for parameters
     within sections.
   * Added -e command line parameter to provide enabled sections from command
   * Added a cleanup of firewall rules on emergency shutdown when unknown
     exception is catched.
   * Fail2ban should not crash now if a wrong file name is specified in
 fail2ban (0.5.4-5) unstable; urgency=low
   * Made failregex'es more specific to don't allow usernames to be used as a
     tool for denial of service attacks. Config files (or at least
     failregex'es) must be updated from this package, otherwise the security
     breach would remain open and only warning gets issued (closes: #330827)
 fail2ban (0.5.4-4) unstable; urgency=low
   * On a request from Calum Mackay added reporting of the enabled sections
 fail2ban (0.5.4-3) unstable; urgency=low
   * Resolved the mistery of debug mode in which commands are not really
     executed: added verbose option to config file, removed -v from
     /etc/default/fail2ban, reordered code a bit so that log targets are
     setup right after background and then only loglevel (verbose,debug) is
     processed, so the warning could be seen in the logs
 fail2ban (0.5.4-2) unstable; urgency=low
   * Now exporting PATH explicitely in init.d/fail2ban script, to avoid
     problems finding iptables in the cases when PATH was not exported outside
     (cfengine, broken shell environment) (closes: #329304)
   * Removed -b from start-stop-daemon because fail2ban detahes on its own
   * Added @localhost to MAIL:from and MAIL:to in fail2ban.conf and placed
     a note to README.Debian regarding necessity to specify full email
     address in MAIL:from (closes: #329722)
   * Added a keyword <section> in parsing of the subject and the body of an
     email sent out by fail2ban (closes: #330311)
 fail2ban (0.5.4-1) unstable; urgency=low
   * New upstream release
 fail2ban (0.5.3-2) unstable; urgency=low
   * Refined comments in README.Debian
   * Reindented init.d script
   P.S. Was not released
 fail2ban (0.5.3-1) unstable; urgency=low
   * New upstream release
 fail2ban (0.5.2-5) unstable; urgency=low
   * Included a patch from Stephen Gildea to provide "status" report by
     init.d script
   * Included a note in README.Debian regarding the fail2ban iptable's
 fail2ban (0.5.2-4) unstable; urgency=low
   * Format of SYSLOG entries is up to the standard now
 fail2ban (0.5.2-3) unstable; urgency=low
   * Fixed errata in /etc/default/fail2ban (closes: #323451)
   * Fixed handling of SYSLOG logging target. Now it can log to any syslog
     target and facility as directed by the config (revisions 160:166 patch
     from syslog branch) (closes: #323543)
   * Included upstream README and TODO
   * Mentioned in README.Debian that apache section is disabled by default
   * Adjusted man pages to cross-reference each other
   * Moved fail2ban man page under section 8 as in upstream
   * Introduced findtime configuration variable to control the lifetime
     of caught "failed" log entries (closes: #323840)
 fail2ban (0.5.2-2) unstable; urgency=low
   * Updated description to reflect flexibility in application of fail2ban
   * Included logrotate (Thanks to Baruch Even)
 fail2ban (0.5.2-1) unstable; urgency=low
   * New upstream release
   * No log4py any more
   * removed -i eth0 from config
 fail2ban (0.5.1-1) unstable; urgency=low
   * New upstream release
 fail2ban (0.5.0-1) unstable; urgency=low
   * New upstream release
   * Libraries placed under /usr/share/fail2ban instead of /usr/lib/fail2ban
   * Corrections to the description of the package
 fail2ban (0.4.1-1) unstable; urgency=low
   * First upstream release of a Debian package
 a18277645ce5599e7eb9138abf76cb48 19878 net optional fail2ban_0.5.4.orig.tar.gz
 ce82320390ac1fecd902f706ea11637a 617 net optional fail2ban_0.5.4-5.14.dsc
 67af13402e93a55f6b6934cea3a89939 14456 net optional fail2ban_0.5.4-5.14.diff.gz
Version: GnuPG v1.2.5 (GNU/Linux)


  to pool/universe/f/fail2ban/fail2ban_0.5.4-5.14.diff.gz
  to pool/universe/f/fail2ban/fail2ban_0.5.4-5.14.dsc
  to pool/universe/f/fail2ban/fail2ban_0.5.4.orig.tar.gz

More information about the ubuntu-changes-auto mailing list