Hello all,
I have written a patch for noble backporting two required commits:
- https://github.com/fail2ban/fail2ban/commit/054e1d89ca3f
- https://github.com/fail2ban/fail2ban/commit/77b052fdea51
I also updated the copyright file to reflect the license of the newly added
files.
I noticed that
** Changed in: fail2ban (Ubuntu Noble)
Assignee: (unassigned) => Ghadi Rahme (ghadi-rahme)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To
Dear all,
This is a remind that new Fail2ban package (1.1.0-2ubuntu2) is still not
available in official apt repo.
Could anyone take care of this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package fail2ban - 1.1.0-2ubuntu2
---
fail2ban (1.1.0-2ubuntu2) oracular; urgency=medium
[ Åka Sikrom (akrosikam) ]
* Add python3-setuptools runtime dependency needed for Python3.12
to use distutils.version (LP: #2055114)
-- Gianfranco
** Changed in: fail2ban (Ubuntu Oracular)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications
As said, fixing oracular first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about this bug go to:
I went through the code, setuptools is needed due to distutils removals
./fail2ban/server/filtersystemd.py:from distutils.version import LooseVersion
./fail2ban/server/filterpyinotify.py:from distutils.version import LooseVersion
Reuploaded, thanks @akrosikam for the help!
** Changed in:
@chris, please check oracular or debian sid, and in that case let me
know. If setuptools is a runtime dependency, this means that devel
release has to be fixed before getting the fix in noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
>OK, I officially give up. Good luck to whomever bothers chasing your
constantly-moving target.
your patch was good, just the rule is to first fix devel, or mark it as
non affected. For an LTS, adding runtime dependencies has to be done
carefully, so this is the reason I'm pedantic, to avoid
confirmed python3-setuptools not being installed with 1.1.0-2 on noble
and oracular...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage
OK, I officially give up. Good luck to whomever bothers chasing your
constantly-moving target.
** Patch removed: "fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch"
Ok, so if this is a runtime dependency, does this mean oracular is not
yet fixed?
fail2ban_1.1.0-2_all.deb
new Debian package, version 2.0.
size 465720 bytes: control archive=10096 bytes.
7008 bytes, 175 lines conffiles
1581 bytes,33 lines
Have just tried this myself in a freshly-created Noble install. I can
confirm Åka Sikrom (akrosikam) is absolutely correct; Python3-setuptools
is a runtime dependency of fail2ban1.0.2-3ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Gianfranco: Done. As expected, fail2ban.service fails to start post-
install, since you excluded an essential part of my patch. See attached
terminal log output.
** Attachment removed: "f2b-costamagnagianfranco-ppa-term-output.log"
I have installed the oracular version (1.1.0-2) on my 3 servers.
Why should I downgrade? failed udate policy
As I know ubuntu LTS, the package will not get any updates for the next
10 years anyway, so I can also install it via dpkg - makes no
difference.
--
You received this bug notification
** Attachment added: "f2b-costamagnagianfranco-ppa-term-output.log"
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5780126/+files/f2b-costamagnagianfranco-ppa-term-output.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I uploaded on my ppa
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa/+packages
please have a look!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
Then I assume you have tested and verified (with a build of the package
which you say you have now uploaded) that fail2ban.service starts
successfully post-install, while python3-setuptools is *not* installed
on your system?
--
You received this bug notification because you are a member of
Uploaded to Ubuntu without the additional dependency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about this bug go to:
** Description changed:
+ [ Impact ]
+ * fail2ban fails to start on Ubuntu 24.04, due to new Python and deprecated
classes (now vendored upstream)
+
+ [ Test Plan ]
+ * Install and check systemctl status fail2ban.
+
+ [ Where problems could occur ]
+ * Nowhere, fixing a program failing to
Because it provides 'distutils' which, as it stands, is a required
runtime module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage
Why, add it as runtime dependency? setuptools is already a build
dependency from what I can see...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To
Changelog added to patch, and patch hereby re-uploaded.
* Bundle required async* modules for python3.12 (Fixes: #2055114)
see upstream commit https://github.com/fail2ban/fail2ban/commit/1024452
* debian/control: Add python3-setutools to Depends
to provide required module 'distutils'
Hello, the patch mentioned in
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/comments/14
looks adding an additional dependency, without explaining why it was added.
Can you please provide more information and also a changelog? It can be changed
later, but a schema of changelog
Okay, I have been looking at all the comments, and provided links in
this thread for a couple hours now, and I'm still not sure what needs to
be done here. I do see there are workarounds, but what does a guy need
to do to make it so that the apt package works with noble? This is a
serious security
Hi,
As a temporary workaround I have personally switch to a docker container
to do the job.
Ofc you must have docker installed and it is not the best option but it
works like a charm for me.
https://docs.linuxserver.io/images/docker-fail2ban/
Waiting as all of you to see a proper fix be
Fortunately for me, I only have to manage a single server and I patched
this problem on that server myself (the comments from Aka Sikrom here
provide some very useful pointers in this regard) so this no longer
matters to me personally. But it's getting embarrassing how long this
simple fix is
having the same issue how do I make it work on Noble version of ubuntu
please help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage
Sylvestre Ledru (sylvestre) for mantic only, not noble ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about this bug go
They should really adopt version 1.1.0. Anything else makes no sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about
I don't know well the Ubuntu processes but I opened this sync request:
https://bugs.launchpad.net/bugs/2065796
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in
Do we have to subscribe to Ubuntu Pro to get an update of this package?
But seriously, what will it take to get this package fixed in Ubuntu?
How can we take Ubuntu seriously on the server is such a fundamental
package remains critically broken?
--
You received this bug notification because
Can this *please* finally be fixed asap? This has been known for more
than two months now, and even before the official release of Ubuntu
24.04 LTS had been made. How this issue is handled for the LTS release
is becoming quite a source of frustration.
--
You received this bug notification
How long till a fix is relreased? Its kinda very important to ubuntu
server system administrator like me. Please do the needful as soon as
possible
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking the Noble task incomplete and unsubscribing ubuntu-sponsors for
now.
** Changed in: fail2ban (Ubuntu Noble)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package fail2ban - 1.1.0-1
---
fail2ban (1.1.0-1) unstable; urgency=medium
* New upstream release
(LP: #2055114)
* Block ssh invalid keys too (Closes: #1038779)
* Follow upstream advice
@fprietog workaround works like a charm ! thank you
wget
https://launchpad.net/ubuntu/+source/fail2ban/1.1.0-1/+build/28291332/+files/fail2ban_1.1.0-1_all.deb
sudo dpkg -i fail2ban_1.1.0-1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ahasenack thank you very much.
In the meantime as a workaround for noble you can install the oracular-
proposed deb file "fail2ban_1.1.0-1_all.deb".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
I uploaded the new version in Debian:
https://tracker.debian.org/news/1524869/accepted-fail2ban-110-1-source-into-unstable/
if someone wants to sync it into Ubuntu, most welcome :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks fossfreedom,
I have tried to go through the documentation you linked to, but its
links to specific processes are either dead or redirect to a new WIP
readthedocs page where the info I need has not been addded yet. Since
this would be my first-ever Ubuntu patch, I need a bit more specific
I see a patch has been added - so I've subscribed ubuntu sponsors.
However, please can the following template be used to describe the
patch, how to test, understand the risks etc.
https://wiki.ubuntu.com/SponsorshipProcess
--
You received this bug notification because you are a member of Ubuntu
Upstream have release a new version which fixes Python 3.12+
compatibility. https://github.com/fail2ban/fail2ban/releases/tag/1.1.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
FWIW, this is what we did in Fedora:
https://src.fedoraproject.org/rpms/fail2ban/c/24c973f252f6d1b4231ee49ee4d5efac785a2fe8?branch=rawhide
i.e., we depend on packages of the asynchat and asyncore libs that were
added to pypi for this kind of purpose -
https://pypi.org/project/pyasynchat/ and
Maintainers: please find attached a new version of my suggested source
patch.
Changes:
* Bundle asyncore.py, asynchat.py and updated asyncserver.py (manual
cherry-pick of upstream commit 1024452)
* Add 'python3-setuptools' to Depends
I have deliberately *not* inserted anything into the
PS: regarding Debian, trixie still ships python3.11 as of today, so this
issue does not apply to them yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04
Maintainers: please find attached a new version of my suggested source
patch.
Changes:
* Bundle asyncore.py, asynchat.py and updated asyncserver.py (manual
cherry-pick of upstream commit 1024452)
* Add 'python3-setuptools' to Depends
I have deliberately *not* inserted anything into the
** Patch removed: "fail2ban-noble-add-bundled-async-python3.12.patch"
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5764439/+files/fail2ban-noble-add-bundled-async-python3.12.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The attachment "fail2ban-noble-add-bundled-async-python3.12.patch" seems
to be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
Maintainers: Here is a suggested source patch for Noble. It is based on
commit no. 1024452 [1] in upstream. This would be my first-ever patch
made for a deb package, so please inspect it carefully for mistakes
if/before you even consider applying it.
Note that 'python3-setuptools' also needs to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about this bug go to:
://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 10 Mar 2024, Åka Sikrom wrote:
> Date: Sun, 10 Mar 2024 12:30:18 -
> From: Åka Sikrom <2055...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
>
> As of
As of this commit from 12 Dec 2023:
https://github.com/fail2ban/fail2ban/commit/1024452fe1befeb5a0a014386a81ec183cd45bb5
upstream ships its source with the missing async* libraries embedded, which
solves the issue for now.
Here is a suggested workaround for Noble until the fix hopefully
I wish people wouldn't use languages like python which changes it's
packages and syntax weekly, but since they do the obvious question, is
anyone going to work on this? It is a rather important security tool.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fail2ban (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
Relevant upstream issue https://github.com/fail2ban/fail2ban/issues/3487
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications
So whilst in Ubuntu we do have python-pyasyncore which provides
asyncore, we don't have asynchat so this might need to be packaged
separately OR vendored into fail2ban
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
asynchat was removed in python 3.12, which just became the default
python3 in 24.04
** Information type changed from Private Security to Public
** Bug watch added: github.com/fail2ban/fail2ban/issues #3487
https://github.com/fail2ban/fail2ban/issues/3487
--
You received this bug
58 matches
Mail list logo
