From 83f7fe4b8402bab171d110703a1b1115efbc9b28 Mon Sep 17 00:00:00 2001 From: Lukasz Kasprzak Date: Tue, 14 Apr 2026 22:32:43 +0200 Subject: cleaned up many scrits and deleted some that were of no use; renamed a lot --- .../action.d/firewallcmd-rich-logging.conf | 29 ---------------------- 1 file changed, 29 deletions(-) delete mode 100644 straper/db/public/fail2ban/etc-fail2ban/action.d/firewallcmd-rich-logging.conf (limited to 'straper/db/public/fail2ban/etc-fail2ban/action.d/firewallcmd-rich-logging.conf') diff --git a/straper/db/public/fail2ban/etc-fail2ban/action.d/firewallcmd-rich-logging.conf b/straper/db/public/fail2ban/etc-fail2ban/action.d/firewallcmd-rich-logging.conf deleted file mode 100644 index 21e4508..0000000 --- a/straper/db/public/fail2ban/etc-fail2ban/action.d/firewallcmd-rich-logging.conf +++ /dev/null @@ -1,29 +0,0 @@ -# Fail2Ban configuration file -# -# Authors: Donald Yandt, Sergey G. Brester -# -# Because of the rich rule commands requires firewalld-0.3.1+ -# This action uses firewalld rich-rules which gives you a cleaner iptables since it stores rules according to zones and not -# by chain. So for an example all deny rules will be listed under _deny and all log rules under _log. -# -# Also this action logs banned access attempts so you can filter that and increase ban time for offenders. -# -# If you use the --permanent rule you get a xml file in /etc/firewalld/zones/.xml that can be shared and parsed easliy -# -# This is an derivative of firewallcmd-rich-rules.conf, see there for details and other parameters. - -[INCLUDES] - -before = firewallcmd-rich-rules.conf - -[Definition] - -rich-suffix = log prefix='f2b-' level='' limit value='/m' - -[Init] - -# log levels are "emerg", "alert", "crit", "error", "warning", "notice", "info" or "debug" -level = info - -# log rate per minute -rate = 1 -- cgit v1.3