On 2024-05-24 14:52:08 +0200, Sylvestre Ledru wrote:
> Could you please propose a PR ? I didn't find the time to fix this lately
> (and i don't use fail2ban anymore).
https://salsa.debian.org/python-team/packages/fail2ban/-/merge_requests/9
This restores the use of nftables and selects the
Le 24/05/2024 à 14:25, Vincent Lefevre a écrit :
On 2024-05-07 08:35:28 +0200, Sylvestre Ledru wrote:
Le 07/05/2024 à 03:57, Vincent Lefevre a écrit :
On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:
May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban
On 2024-05-07 08:35:28 +0200, Sylvestre Ledru wrote:
>
> Le 07/05/2024 à 03:57, Vincent Lefevre a écrit :
> > On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:
> > > May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226
> > > fail2ban[557228]: ERROR Failed
Le 07/05/2024 à 03:57, Vincent Lefevre a écrit :
On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:
May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban
[557228]: ERROR Failed during configuration: Have not found any
log file for sshd jail
I
On 2024-05-07 03:57:44 +0200, Vincent Lefevre wrote:
> sshd_backend = systemd
BTW, that would fix the issue only for sshd. But what about the other
jails the user could have enabled in /etc/fail2ban/jail.local? The
user configuration may rely on systemd being the default backend, at
least the
On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:
> May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban
>[557228]: ERROR Failed during configuration: Have not found
> any log file for sshd jail
I suppose that this is because sshd no longer uses the
Package: fail2ban
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
After the upgrade to 1.1.0-1, "systemctl status" gives
× fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; preset:
enabled)
Active: failed
7 matches
Mail list logo
