[Bug 2055114] Re: fail2ban is broken in 24.04 Noble

[Andreas Hasenack]

New version is in oracular-proposed[1]:

fail2ban (1.1.0-1) unstable; urgency=medium

  * New upstream release
    (LP: #2055114)
  * Block ssh invalid keys too (Closes: #1038779)
  * Follow upstream advice
    https://github.com/fail2ban/fail2ban/issues/3292#issuecomment-2078361360
    to only have sshd as enabled = true in jail.d_defaults-debian.conf
  * Update lintian override info format in d/source/lintian-overrides on line 1-2.
  * Update standards version to 4.6.2, no changes needed.

 -- Sylvestre Ledru <sylvestre at debian.org>  Thu, 02 May 2024 13:57:06
+0200

Nothing needs to be sponsored for the ubuntu devel release now. I'll
mark it as fix committed, since it was uploaded.

Noble is still affected, so I'm adding a noble task. This then needs to
become an SRU, following [2], before anything can be uploaded to noble.


1. https://launchpad.net/ubuntu/+source/fail2ban/1.1.0-1
2. https://wiki.ubuntu.com/StableReleaseUpdates

** Bug watch added: github.com/fail2ban/fail2ban/issues #3292
   https://github.com/fail2ban/fail2ban/issues/3292

** Also affects: fail2ban (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: fail2ban (Ubuntu Oracular)
   Importance: Undecided
       Status: Confirmed

** Changed in: fail2ban (Ubuntu Oracular)
       Status: Confirmed => Fix Committed

** Changed in: fail2ban (Ubuntu Noble)
       Status: New => Confirmed

** Changed in: fail2ban (Ubuntu Noble)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055114

Title:
  fail2ban is broken in 24.04 Noble

Status in fail2ban package in Ubuntu:
  Fix Committed
Status in fail2ban source package in Noble:
  Confirmed
Status in fail2ban source package in Oracular:
  Fix Committed

Bug description:
  Was working in 22.04, but after upgrading to 24.04 I get this:

  × fail2ban.service - Fail2Ban Service
       Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; preset: enabled)
       Active: failed (Result: exit-code) since Sun 2024-02-25 02:27:29 PST; 1 day 18h ago
     Duration: 2.330s
         Docs: man:fail2ban(1)
      Process: 1130 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
      Process: 1133 ExecStart=/usr/local/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
     Main PID: 1133 (code=exited, status=255/EXCEPTION)
          CPU: 660ms

  Feb 25 02:27:26 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban Service...
  Feb 25 02:27:26 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service.
  Feb 25 02:27:28 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban                [1133]: ERROR   No module named 'asynchat'
  Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
  Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Failed with result 'exit-code'.

  grep fail2ban syslog
  2024-02-25T02:25:17.813593-08:00 mx1 systemd[1]: Stopping fail2ban.service - Fail2Ban Service...
  2024-02-25T02:27:26.625640-08:00 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban Service...
  2024-02-25T02:27:26.678572-08:00 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service.
  2024-02-25T02:27:28.954548-08:00 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban                [1133]: ERROR   No module named 'asynchat'
  2024-02-25T02:27:29.004733-08:00 mx1 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
  2024-02-25T02:27:29.004834-08:00 mx1 systemd[1]: fail2ban.service: Failed with result 'exit-code'.

  Seems 24.04 is missing a python 3.12 module 'asynchat'.

  This leaves my systems vulnerable to brute-force password guessing
  attacks.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: fail2ban 1.0.2-3
  Uname: Linux 6.7.6 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Mon Feb 26 20:33:12 2024
  InstallationDate: Installed on 2017-08-14 (2388 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: fail2ban
  UpgradeStatus: Upgraded to noble on 2024-01-23 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions