FS#54116 - [fail2ban] Include c7ddf1f940aa30f7d31dc1bf6e4d895713a6e38b into package

Attached to Project: Community Packages
Opened by Noel Kuntze (thermi) - Friday, 19 May 2017, 14:34 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 15 December 2017, 16:13 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Commit c7ddf1f940aa30f7d31dc1bf6e4d895713a6e38b[1] on the github repo for fail2ban
fixes a bug in fail2ban 0.9 that causes fail2ban to stop working.

The problem is that fail2ban doesn't close file descriptors that the journald backend uses,
when fail2ban-daemon reloads its configuration (stops all jails and starts them again).

Corresponding issue: https://github.com/fail2ban/fail2ban/issues/991

I chose severity High, because it stops the fail2ban daemon from working and it has to be restarted to fix the problem.

[1] https://github.com/fail2ban/fail2ban/commit/c7ddf1f940aa30f7d31dc1bf6e4d895713a6e38b

Steps to reproduce:

Reload the fail2ban systemd unit a dozen times and watch the fail2ban logs.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 15 December 2017, 16:13 GMT
Reason for closing:  None
Additional comments about closing:  0.10 is now in Arch
Comment by Doug Newgard (Scimmia) - Friday, 19 May 2017, 15:02 GMT
Looks like this is included in the latest release?

Edit: nevermind, different issue
Comment by Noel Kuntze (thermi) - Friday, 19 May 2017, 15:12 GMT
The fix is a backport from 0.10, which isn't shipped in Arch yet. If Arch starts shipping 0.10, we don't need this fix. If we don't start shipping 0.10, we need it. It might maybe be in the next release, but patching it now is better than patching it later.

Loading...