Bug 16303 - fail2ban doesn't remove iptables rules when stopping
Summary: fail2ban doesn't remove iptables rules when stopping
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-07-06 12:43 CEST by Marc Krämer
Modified: 2017-07-31 11:45 CEST (History)
1 user (show)

See Also:
Source RPM: fail2ban-0.8.13-5.mga5.noarch
CVE:
Status comment:


Attachments

Description Marc Krämer 2015-07-06 12:43:53 CEST
stop script of fail2ban is improperly:

iptables rules don't get removed after stop

this causes the restart script to add the same rules again

Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-07-06 12:47:10 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

Comment 2 Marc Krämer 2015-07-06 12:48:49 CEST
sorry, I forgot, bugzilla didn't name the package with the subject itself
Comment 3 Samuel Verschelde 2015-07-06 12:49:49 CEST
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

Comment 4 Marja Van Waes 2017-07-29 23:52:08 CEST
(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
CC: (none) => marja11
Status: ASSIGNED => NEW
Keywords: (none) => NEEDINFO

Comment 5 Marc Krämer 2017-07-31 11:45:22 CEST
this bug is fixed in mag6.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.