On Wed, 2023-09-27 at 09:48 -0500, Ian Pilcher wrote: > On 9/27/23 04:56, Miro Hrončok wrote: > > fail2ban > > ======== > > https://bugzilla.redhat.com/2219991 > > https://github.com/fail2ban/fail2ban/issues/3487 > > Bugzilla ASSIGNED 2 months ago, no update since. > > Maintainers NEEDINFOed last week. > > With my system/network administrator hat on, this one is really > concerning. After reading the upstream issue, it doesn't seem that > there's much chance of this being fixed any time soon. > > Is there anything in Fedora that provides similar functionality? (I've > looked, but come up empty thus far.) Could we possibly just vendor the old async stuff into fail2ban for now to keep it usable until upstream manages to rewrite everything? I agree that we should really try to avoid this dying, it does seem to be fairly commonly used by enthusiast sysadmins. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
