Latest upstream release: 0.10.0a1 Current version/release in rawhide: 0.9.4-5.fc25 URL: http://www.fail2ban.org/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/6602/
Patching or scratch build for fail2ban-0.9.4 failed.
Created attachment 1179792 [details] Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.
Patches were not touched. All were applied properly
And it has IPv6 support! Yay!
0.10 final was released in August. Is it possible to see this in Fedora 26 and later?
fail2ban-0.10.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-af238d8e30
Let's let it get tested in F27+ for a bit first.
fail2ban-0.10.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-af238d8e30
Currently there is for dovecot a line " ^pam\(\S+,<HOST>\): pam_authenticate\(\) failed: (User not known to the underlying authentication module: \d+ Time\(s\)|Authentication failure \(password mismatch\?\))\s*$" This does not catch all things (for me nothing), I have to have " ^pam\(\S+,<HOST>,\S+\): pam_authenticate\(\) failed: Permission denied\s*$" as well. Beyond that, things seem to be working.
Emails saying the rules are up are having problems in the subject "[Fail2Ban] prosody: started on <fq-hostname>" (yes, the prosody rule is mine, but it is happening on all rules, not sure why yet). With 0.9x it works.
(In reply to Trever Adams from comment #9) > Currently there is for dovecot a line " ^pam\(\S+,<HOST>\): > pam_authenticate\(\) failed: (User not known to the underlying > authentication module: \d+ Time\(s\)|Authentication failure \(password > mismatch\?\))\s*$" > This does not catch all things (for me nothing), I have to have " > ^pam\(\S+,<HOST>,\S+\): pam_authenticate\(\) failed: Permission denied\s*$" > as well. This should be reported upstream - https://github.com/fail2ban/fail2ban/issues
(In reply to Trever Adams from comment #10) > Emails saying the rules are up are having problems in the subject > "[Fail2Ban] prosody: started on <fq-hostname>" (yes, the prosody rule is > mine, but it is happening on all rules, not sure why yet). With 0.9x it > works. Presumably /var/log/fail2ban.log should have more information.
Both have been reported upstream.
fail2ban-0.10.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
Please see https://github.com/fail2ban/fail2ban/issues/1859 for information on fixing one of the two bugs this version introduces. It was fixed before I reported it, but not in Fedora.
Is there a chance to see fail2ban 0.10 for Fedora 25 or 26?