Package: fail2ban
Version: 0.5.2-1
Severity: grave
Tags: patch
Justification: renders package unusable
Hope this isn't a duplicate--reportbug isn't showing me any known issues
for some reason.
The iptables blocking in fail2ban consistently fails to work because the
iptables command is not in the execution path. This means that the
package is completely inoperable when using iptables, which I believe is
the most common choice for Debian systems.
The "patch" is to edit /etc/fail2ban.conf:
s/iptables/\/sbin\/iptables/g
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages fail2ban depends on:
ii iptables 1.3.1-2 Linux kernel 2.4+ iptables adminis
ii python 2.3.5-2 An interactive high-level object-o
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
