ClearOS Bug Tracker

Main | My View | View Issues | Change Log | Roadmap | Repositories
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0015701ClearOSapp-attack-detector - Attack Detectorpublic2017-07-12 08:392021-11-09 05:39
Reporteruser2 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionwon't fix 
PlatformOSOS Version
Product Version7.3.1 
Target VersionFixed in Version 
Summary0015701: Tidy up if fail2ban is stopped
DescriptionIf fail2ban is stopped, it should tidy up any existing rules or at least remove the firewall hook. As it stands, the rules will stay in place until the firewall is restarted.

Note: fail2ban takes a looong time to regenerate rules, so it would be good to differentiate between a "stop" and a "restart" (which is often coded as a "stop / start").
TagsNo tags attached.
Attached Filestxt file icon firewall.txt [^] (11,612 bytes) 2017-07-13 13:02 [Show Content]
txt file icon firewall1.txt [^] (8,835 bytes) 2017-07-13 13:03 [Show Content]

- Relationships

-  Notes
(0005851)
NickH (developer)
2017-07-13 13:06

 This is a WFM on 7.3 with f2b 0.9.5-3. See the file firewall.txt with f2b running and firewall1.txt after stopping it.

The only "f2b native" way round this is to go towards ipset rules and use the ipset timeout feature. This improves the start up times and allows you to just destroy the set on stopping rather than delete the rules one by one.
(0015981)
NickH (developer)
2021-11-09 05:39

 Ipset lists are now used and work in the backgrouns in an unobtrusive way

- Issue History
Date Modified Username Field Change
2017-07-12 08:39 user2 New Issue
2017-07-12 08:40 user2 Status new => confirmed
2017-07-13 13:02 NickH File Added: firewall.txt
2017-07-13 13:03 NickH File Added: firewall1.txt
2017-07-13 13:06 NickH Note Added: 0005851
2021-11-09 05:39 NickH Note Added: 0015981
2021-11-09 05:39 NickH Status confirmed => closed
2021-11-09 05:39 NickH Resolution open => won't fix