Confirmed that this is still annoying. I (as a moderate linux user) had
to search several hours, during several days until finding the fix.
It works fine in a debian11 fresh install, not in a debian12. So I
suppose it was fixed some time before, but came back an issue recently.
After
This bug report from 2014 is meanwhile more important than ever.
With the latest stable release Debian marked rsyslog as deprecated (see
https://wiki.debian.org/Rsyslog).
If a user removes the rsyslog package without removing the related
logfiles in /var/log, fail2ban silently stops doing
Hi Team,
This is getting pretty annoying, a 9 years old inconvenience, especially
now that Debian 12 does not even have a syslog service installed by default.
Fail2ban fails to start right after its installation.
The solution is really trivial. At least an SSHD override should be added
in
Hi all,
Still an issue for the backend option being left on 'auto', could the
default for Debian be changed to use systemd as the backend?
(Fresh install on Bookworm).
Regards,
Nephi.Aust
Hi,
in Debian 11 with f2b version 0.11.2-2 the issue with "journalmatch" seems to
be fixed, but now the filter is wrong.
/etc/fail2ban/filter.d/sshd.conf
# consider failed publickey for invalid users only:
cmnfailre-failed-pub-invalid = ^Failed publickey for invalid user
(?P\S+)|(?:(?! from
Install rsyslog? Nonsense.
Creating /etc/fail2ban/jail.local with
[DEFAULT]
default_backend = systemd
will do the trick.
IMO the error lies within /etc/fail2ban/paths-common.conf which says
[DEFAULT]
default_backend = auto
This should be changed to
default_backend = systemd
For people looking for an easy work around:
apt-get install rsyslog
will ensure sshd is logged as usual.
Based on the fail2ban changelog, it looks like fail2ban added support
for systemd in 0.9.0. The stretch repos include 0.9.2-1.
source: https://github.com/fail2ban/fail2ban/blob/master/ChangeLog
It seems a shame that the Debian base system moved to systemd but left
fail2ban behind.
Also a shame
Hi,
after upgrading my servers to jessie and journald, I’m also interested
in having fail2ban working again. If this bug is fixed, I would greatly
appreciate an upload to jessie-backports.
Thanks,
Joachim
--
Joachim nomeata Breitner
Debian Developer
nome...@debian.org | ICQ# 74513189 |
Package: fail2ban
Version: 0.9.1-1
Severity: important
Dear Maintainer,
when a system is configured to use the systemd journal as the
sole logging system, i.e. when none of the packages provided by
system-log-daemon are installed, the default sshd jail does not work.
When logging in the system
10 matches
Mail list logo
