Package: fail2ban Version: 0.10.2-2.1 Severity: important Dear Maintainer,
After clean installation of Fail2Ban on buster or after upgrade from stretch to buster (this doesn't matter), all configuration files in /etc/fail2ban/ that is suffixed with .local is not taken by Fail2Ban instance. That was a normal configuration method and still is for Fail2Ban. It causes that Fail2Ban dosen't work at all because don't add any chains to iptables. -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fail2ban depends on: ii lsb-base 10.2019051400 ii python3 3.7.3-1 Versions of packages fail2ban recommends: ii iptables 1.8.2-4 ii nftables 0.9.0-2 ii python 2.7.16-1 pn python3-pyinotify <none> pn python3-systemd <none> ii whois 5.4.3 Versions of packages fail2ban suggests: ii mailutils [mailx] 1:3.5-3 pn monit <none> ii rsyslog [system-log-daemon] 8.1901.0-1 pn sqlite3 <none>
