Your message dated Thu, 20 Mar 2014 21:42:06 -0400 with message-id <[email protected]> and subject line [[email protected]: fail2ban_0.8.13-1_amd64.changes ACCEPTED into unstable] has caused the Debian Bug report #739364, regarding fail2ban: Filter apache-common.conf is broken it and any other filter that depends on it doesn't work. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 739364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739364 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: fail2ban Version: 0.8.11-1 Severity: important Dear Maintainer, What led up to the situation? Using any of the apache filters listed below. What was the outcome of this action? Using the current version of apache-common.conf fails to find the client ipaddress. What exactly did you do (or not do) that was effective. Changing the definition in apache.common.conf to the current fail2ban git version fixes it. apache-common.conf is just a predefined variable that is used in other filters. The current definition is: _apache_error_client = \[[^]]*\] \[(error|\S+:\S+)\]( \[pid \d+:\S+ \d+\])? \[client <HOST>(:\d{1,5})?\] It doesn't work and should be changed to: _apache_error_client = \[[^]]*\] \[(:?error|\S+:\S+)\]( \[pid \d+(:\S+ \d+)?\])? \[client <HOST>(:\d{1,5})?\] This works and is the current fail2ban git definition. All these apache filters depend on apache-common.conf apache-auth.conf apache-common.conf apache-nohome.conf apache-noscript.conf apache-overflows.conf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fail2ban depends on: ii lsb-base 4.1+Debian12 pn python:any <none> Versions of packages fail2ban recommends: ii iptables 1.4.21-1 ii python-pyinotify 0.9.4-1 ii whois 5.1.1 Versions of packages fail2ban suggests: ii bsd-mailx [mailx] 8.1.2-0.20131005cvs-1 ii python-gamin 0.1.10-4.1 ii rsyslog [system-log-daemon] 7.4.4-1 -- Configuration Files: /etc/fail2ban/action.d/shorewall.conf changed [not included] /etc/fail2ban/fail2ban.conf changed [not included] /etc/fail2ban/filter.d/apache-common.conf changed [not included] /etc/fail2ban/jail.conf changed [not included] /etc/logrotate.d/fail2ban changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---Version: 0.8.12-1 Forgot to include the changelog for prev UNRELEASED upstream release which addressed closed above issues: fail2ban (0.8.12-1) UNRELEASED; urgency=low * New upstream release - provides "fail2ban-client flushlogs" command, debian/fail2ban.logrotate was adjusted to use it. Helps to mitigate #697333 - removes indentation of name and loglevel while logging to SYSLOG (Closes: #730202) - fixes apache-common.conf (Closes: #739364) * /etc/default/fail2ban -- minor typo. Thanks Vincent Lefevre for report (Closes: #734421) * debian/patches: - dropping cherry-picked changeset* -- Yaroslav Halchenko <[email protected]> Fri, 07 Feb 2014 00:45:38 -0500 ----- Forwarded message from Debian FTP Masters <[email protected]> ----- Date: Fri, 21 Mar 2014 01:33:23 +0000 From: Debian FTP Masters <[email protected]> To: Yaroslav Halchenko <[email protected]> Subject: fail2ban_0.8.13-1_amd64.changes ACCEPTED into unstable Accepted: Format: 1.8 Date: Tue, 18 Mar 2014 23:13:35 -0400 Source: fail2ban Binary: fail2ban Architecture: source all Version: 0.8.13-1 Distribution: unstable Urgency: low Maintainer: Yaroslav Halchenko <[email protected]> Changed-By: Yaroslav Halchenko <[email protected]> Description: fail2ban - ban hosts that cause multiple authentication errors Changes: fail2ban (0.8.13-1) unstable; urgency=low . * New upstream bug-fix release: but consider 0.9.0 (to be uploaded to experimental) * debian/jail: - new jail definitions: apache-modsecurity, apache-nohome, freeswitch, ejabberd-auth, ssh-blocklist, nagios - new configuration option: ignorecommand * debian/post{inst,rm},preinst: - [thanks to Daniel Schaal]: take care about renaming config files - firewall-cmd-direct-new.conf to firewallcmd-new.conf which happened in 0.8.11-29-g56b6bf7 - lighttpd-fastcgi.conf to suhosin.conf and sasl.conf to postfix-sasl.conf in the past 0.8.11 release Checksums-Sha1: 9b933c9e1d6cf3ce17b3e363b3161609ad1e7a51 1215 fail2ban_0.8.13-1.dsc 2a2ddffb6e60e2997dcceb0ac25761aa6931f5f6 226716 fail2ban_0.8.13.orig.tar.gz 70ba681cfa68e68b4508c8bea8e5467f4c1bc2e3 29376 fail2ban_0.8.13-1.debian.tar.xz d50ad0fed3d07143363d033a2ec0cbedd477e7bb 165378 fail2ban_0.8.13-1_all.deb Checksums-Sha256: 326d53eb4db17719583671210b9092646a4c660a73657b8850f04847284f29c2 1215 fail2ban_0.8.13-1.dsc 0cfef3dab6ed3a3a91fd977f2d61f7c13c557d9510d18fd098bdec10ea23f3c8 226716 fail2ban_0.8.13.orig.tar.gz 1c41542933054229aca4a3754dd3bde30cd7e490c579255f69efc348d00d2c88 29376 fail2ban_0.8.13-1.debian.tar.xz 42537947e8fcfc0951b8511f26f35a92fa070994e73a46d2f7ce6842f6be96ea 165378 fail2ban_0.8.13-1_all.deb Files: 4528da7d80ffb24c5eeb1eab3855d148 1215 net optional fail2ban_0.8.13-1.dsc 25d1f9ac57258cc803231dff0d1ba3f4 226716 net optional fail2ban_0.8.13.orig.tar.gz d7c76dda24ef2fb5300149ed37fd4935 29376 net optional fail2ban_0.8.13-1.debian.tar.xz b0b9a415794d02acab6b19753a1ecd9e 165378 net optional fail2ban_0.8.13-1_all.deb Thank you for your contribution to Debian. ----- End forwarded message ----- -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
--- End Message ---
