Package: fail2ban Version: 0.10.2-2.1 Followup-For: Bug #888711 Dear Maintainer,
fail2ban 0.10.2-2.1 still ships the incorrect sshd-ddos.conf and sshd-aggressive.conf files. Neither ddos nor aggressive are defined parameters so these files should be rewritten as shown in the attachements, that is by simply setting mode to the desired value: mode = ddos and mode = aggressive respectively. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US (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 ii python3-pyinotify 0.9.6-1 ii python3-systemd 234-2+b1 ii whois 5.4.3 Versions of packages fail2ban suggests: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1 ii mailutils [mailx] 1:3.5-3 pn monit <none> ii rsyslog [system-log-daemon] 8.1901.0-1 ii sqlite3 3.27.2-3 -- Configuration Files: /etc/fail2ban/filter.d/sshd-aggressive.conf changed: [INCLUDES] before = sshd.conf [Definition] mode = aggressive /etc/fail2ban/filter.d/sshd-ddos.conf changed: [INCLUDES] before = sshd.conf [Definition] mode = ddos -- no debconf information
