Control: tags -1 - trixie sid Control: severity -1 normal
On Thu, 11 Jan 2024 00:15:27 +0100 Luca Capello <l...@pca.it> wrote: [...]
Alban, 0.9.6-2 is quite an old version and you reported the bug more than 5 years, can you try on a more up-to-date Debian?
This is no longer a bug on unstable/trixie. I have run the following tests to confirm. I created a fresh VM with Debian unstable and installed fail2ban. Running `systemctl status fail2ban` shows that fail2ban is successfully running. Reboot the machine and fail2ban is still running. Started monitoring /var/log/fail2ban.log. Then from the host machine connected using SSH client. At the password prompt, entered wrong password. For each incorrect password attempt, a message is printed in fail2ban.log with the client's IP address. After 5 such messages, a ban message was printed and the client was unable to connect and connect was refused. A few minutes later, the client was unbanned and was able to connect again.
On Debian bookworm, I could confirm that the problem still exists. fail2ban fails to start with 'ERROR: Failed during configuration: Have not found any log file for sshd jail'. This is because /var/log/auth.log does not exist due to journald being the default. Setting backend = systemd fixes this issue and I have tested this similar to unstable setup. So, if the fix for #770171 is backported to bookworm, then this issue can be closed.
When bug #1061776 was merged into this bug, the severity was inadvertently raised to 'serious' again. Due to serious severity the package was removed from testing and with it the freedombox package (which depends on fail2ban). I am setting the serverity back to normal as this is not a problem worth removing fail2ban package and its depends for. The package is usable when default configuration is modified as in case of FreedomBox setups.
-- Sunil
OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
