| Summary: | fail2ban doesn't remove iptables rules when stopping | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | fail2ban-0.8.13-5.mga5.noarch | CVE: | |
| Status comment: | |||
|
Description
Marc Krämer
2015-07-06 12:43:53 CEST
Thanks for the report. Some tips about bug reporting: the subject must be understandable when read out of any context. "Stop improperly" is not a good subject. "fail2ban doesn't remove iptables rules when stopping" would be better. Or "fail2ban restart adds duplicated iptable rules to existing ones". I let you rephrase the subject.
Marc Krämer
2015-07-06 12:48:05 CEST
Summary:
Stop improperly =>
fail2ban doesn't remove iptables rules when stopping sorry, I forgot, bugzilla didn't name the package with the subject itself Assigning to maintainer. Assignee:
bugsquad =>
remco
Remco Rijnders
2015-07-06 13:04:36 CEST
Status:
NEW =>
ASSIGNED
Remco Rijnders
2017-07-24 14:00:22 CEST
Assignee:
remco =>
bugsquad (In reply to Samuel Verschelde from comment #3) > Assigning to maintainer. re-assigning to all packagers collectively. @ M K Is this bug still valid in a fully updated system? If so, for which Mageia version(s)? Assignee:
bugsquad =>
pkg-bugs this bug is fixed in mag6. Status:
NEW =>
RESOLVED |