Your message dated Sat, 17 Aug 2024 07:18:58 +0000
with message-id <e1sfdie-0084be...@fasolo.debian.org>
and subject line Bug#1078208: fixed in fail2ban 1.1.0-6
has caused the Debian Bug report #1078208,
regarding fail2ban: sshd.conf filter does not work with OpenSSH 9.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1078208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fail2ban
Version: 1.1.0-4
Severity: serious
Tags: upstream fixed-upstream
The fail2ban sshd.conf filter does not works with OpenSSH 9.8.
This is due to
openssh (1:9.8p1-1) unstable; urgency=medium
* New upstream release (https://www.openssh.com/releasenotes.html#9.8p1):
[...]
- sshd(8): several log messages have changed. In particular, some log
messages will be tagged with as originating from a process named
"sshd-session" rather than "sshd".
This was fixed upstream several weeks ago:
https://github.com/fail2ban/fail2ban/pull/3782
As seen at https://github.com/fail2ban/fail2ban/pull/3782/files
the change is quite simple: change
_daemon = sshd
to
_daemon = sshd(?:-session)?
(As sshd.conf is a conffile, the user might already fix this on his
side, but it must be correct by default, in particular for the next
Debian release.)
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'),
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.10.3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fail2ban depends on:
ii python3 3.12.4-1
ii python3-systemd 235-1+b4
Versions of packages fail2ban recommends:
ii iptables 1.8.10-4
ii nftables 1.1.0-2
ii python3-pyinotify 0.9.6-3
ii whois 5.5.23
Versions of packages fail2ban suggests:
ii mailutils [mailx] 1:3.17-2+b1
pn monit <none>
ii sqlite3 3.46.0-1
pn system-log-daemon <none>
-- no debconf information
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 1.1.0-6
Done: Sylvestre Ledru <sylves...@debian.org>
We believe that the bug you reported is fixed in the latest version of
fail2ban, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1078...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru <sylves...@debian.org> (supplier of updated fail2ban package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 17 Aug 2024 07:40:22 +0100
Source: fail2ban
Architecture: source
Version: 1.1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Sylvestre Ledru <sylves...@debian.org>
Closes: 1078208
Changes:
fail2ban (1.1.0-6) unstable; urgency=medium
.
* Adjust the ssh configuration to work with openssh 9.8
(closes: #1078208)
Thanks to Vincent Lefèvre for the patch
Checksums-Sha1:
897650179eee8bf86ec18e752ab4c4fc54000e18 2054 fail2ban_1.1.0-6.dsc
3655868b378e6e2782bea5122136c9e1d2b1dee0 30596 fail2ban_1.1.0-6.debian.tar.xz
7b00f9986af0f57e0587a1391f67263e042776bb 6502 fail2ban_1.1.0-6_amd64.buildinfo
Checksums-Sha256:
480a90353932d9e2837b3d4497890b7dfe6a26b6d5b465e3e2e5dfaf10c176c5 2054
fail2ban_1.1.0-6.dsc
eeb32d4ec117e485a31f8687ff4219f77777da37d6bbe01ff336c06597d6b288 30596
fail2ban_1.1.0-6.debian.tar.xz
10a5573e4dab562926ba77791a6cbc1ba7c4f433add77814c47c64a9fda0b55c 6502
fail2ban_1.1.0-6_amd64.buildinfo
Files:
1def2099531002521e910ab4009b5eba 2054 net optional fail2ban_1.1.0-6.dsc
9c31175feff48d4fa4618f452ea66bd3 30596 net optional
fail2ban_1.1.0-6.debian.tar.xz
2e8523c24d1e5799ad629ec1960bfb9f 6502 net optional
fail2ban_1.1.0-6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmbASdQACgkQfmUo2nUv
G+FKVxAAh1hb7ZVDaFTmF5birVFhEYAWxDpceopM4Vf/4KiQfFgMpsqNRBi4StJF
B7a32Jn8iZVP2ou+W7O8EAyaZWaqbeZLDBrT3HhBZ/NXh5K3PUzU0rONGE0lvuIM
UrG65QXbp8J5mVAEku//q+ZRgkVF2UOOrFWxPE1Uty4mo2ywdGtd1sfZcNtkWDLx
WpWrHjd+Om9DH0Sjfov7v3KX1uFrmF+2T7On25Jo0C0vdSOW3uZU8ScjBU7aWqGl
NdlwUH/Wk0/6qtromm0kKS/0ke+4nVtaqMJrpKlbQhMfHTfb3DFRxVZ3JC7nE+1J
R2BP2QQwkrEkFnMFLiNVd3rcuUOax3gTiGQG3Z4Rlw88QxGYEn1KZL+D3aycpBPU
fEe1qjERooq5MDOKMnwQ5++pEykt8I4qeDG9UYMThFBVkSmXhw9tp/9kf55yyfvt
8hHRCp7FbeJz/gXT4VOs0aCXHT8k9GNjZSUjBYRYDSi2x+f5VADW1rRm6K9i2xE9
KYXyMXSeN0eDIx7dMy0ObvPNjonhtATy4b8YwLwBBRkF22ZBIbIXcMpmvJaZg3fp
c11Lc3VwCSQYNJbJPYkNGjAjip0PE+SQa0qf1aHRX0yerxV456DONWMWZkZetnWC
KnXYoMh1Xj7XR7LYn5QTMT42k2mBwm6tj0UsYx0usuHOgFpSTvs=
=7O/1
-----END PGP SIGNATURE-----
pgpJAN02oY33p.pgp
Description: PGP signature
--- End Message ---
