Package: fail2ban
Version: 0.8.6-3wheezy3
Severity: minor
Tags: patch
Dear Maintainer,
the script /etc/logrotate.d/fail2ban sets logtarget to /var/log/fail2ban.log.
This may override different settings in the main configuration
(/etc/fail2ban/fail2ban.conf) or via cli. IMHO a logrotate script should never
override a main configuration file. The attached patch changes this behavior.
The logtarget ist (re)set to the current logtarget.
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (950, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
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+Debian8+deb7u1
ii python 2.7.3-4+deb7u1
ii python-central 0.6.17
Versions of packages fail2ban recommends:
ii iptables 1.4.14-3.1
pn python-gamin <none>
ii whois 5.1.1~deb7u1
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20111106cvs-1
-- Configuration Files:
/etc/logrotate.d/fail2ban changed [not included]
-- no debconf information
--- fail2ban.org 2012-06-05 10:57:57.306325291 +0200
+++ fail2ban 2012-06-05 10:58:56.458340504 +0200
@@ -7,7 +7,7 @@
delaycompress
missingok
postrotate
- fail2ban-client set logtarget /var/log/fail2ban.log >/dev/null
+ fail2ban-client set logtarget $(fail2ban-client get logtarget | tail -1 | cut -f 2 -d ' ') >/dev/null
endscript
create 640 root adm
}
