| Summary: | Backport Request: Update fail2ban in Stable to a recent version | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | jeffrobinsSAE, lovaren, mageia, marja11, smelror |
| Version: | 6 | Keywords: | Backport |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | fail2ban | CVE: | |
| Status comment: | |||
|
Description
Kristoffer Grundström
2014-10-03 16:04:19 CEST
Kristoffer Grundström
2014-10-03 16:04:34 CEST
CC:
(none) =>
kristoffer.grundstrom1983
Manuel Hiebel
2014-10-06 10:00:46 CEST
Assignee:
bugsquad =>
remco Version 0.9.1 has been available for months. Component:
Backports =>
RPM Packages Where? rpm.pbone.net doesn't say that Mageia 4 or Cauldron have 0.9.1. (In reply to Samuel VERSCHELDE from comment #1) > Version 0.9.1 has been available for months. (In reply to Kristoffer Grundström from comment #2) > Where? rpm.pbone.net doesn't say that Mageia 4 or Cauldron have 0.9.1. He means available upstream (he would have closed this report if we had 0.9.1 We have fail2ban-0.8.13-5.mga5.noarch.rpm in cauldron CC:
(none) =>
marja11 Has any progress been made on this? I just setup a new system and went to go use fail2ban, but our version (0.8.13) isn't compatible with systemd, since no logfiles are created (messages, auth.log, etc). I have an old system running Mageia 5 that does create the log files, which means fail2ban 0.8.13 works. I just can't remember what I installed that gave me back the logfiles. I debated putting security as a keyword, since missing fail2ban does open up a hole by allowing ssh brute force attacks in a much shorter amount of time. CC:
(none) =>
jeffrobinsSAE (In reply to Jeff Robins from comment #4) > Has any progress been made on this? I just setup a new system and went to > go use fail2ban, but our version (0.8.13) isn't compatible with systemd, > since no logfiles are created (messages, auth.log, etc). We have fail2ban-0.9.5-1.mga6 in cauldron now, and this bug report was filed against cauldron. However, I understand you are running Mageia 5, since you added "5.1" as Keyword. Changing version to Mageia 5 > > I have an old system running Mageia 5 that does create the log files, which > means fail2ban 0.8.13 works. I just can't remember what I installed that > gave me back the logfiles. @ Remmy Do you have an idea? > > I debated putting security as a keyword, since missing fail2ban does open up > a hole by allowing ssh brute force attacks in a much shorter amount of time. CC'ing all packagers collectively, in case the maintainer is unavailable. Version:
Cauldron =>
5 fail2ban is available as 0.9.5 in mga6. the newest 0.10 version is now available with the long awaited ipv6 support: https://github.com/fail2ban/fail2ban/blob/0.10/ChangeLog it would be great to have this update available CC:
(none) =>
mageia (In reply to Marc Krämer from comment #6) > fail2ban is available as 0.9.5 in mga6. > the newest 0.10 version is now available with the long awaited ipv6 support: > https://github.com/fail2ban/fail2ban/blob/0.10/ChangeLog > > it would be great to have this update available Doesn't it need agreement on dev ml to push it to stable? Maybe kekepower (who pushed fail2ban-0.10.3.1 to cauldron) is willing to push it to 6/backports_testing? CC:
pkg-bugs =>
smelror as far as I've read the backport policy, only the maintainer or another packager decides if he's willing to do the backport. Keywords:
(none) =>
Backport closed as old Resolution:
(none) =>
OLD |