View | Details | Raw Unified | Return to bug 223069 | Differences between
and this patch

Collapse All | Expand All

(-)Makefile (+1 lines)
Lines 2-7 Link Here
2
2
3
PORTNAME=	fail2ban
3
PORTNAME=	fail2ban
4
PORTVERSION=	0.10.1
4
PORTVERSION=	0.10.1
5
PORTREVISION=   1
5
CATEGORIES=	security python
6
CATEGORIES=	security python
6
PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
7
PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
7
8
(-)files/patch-config_action.d_pf.conf (+20 lines)
Line 0 Link Here
1
--- config/action.d/pf.conf.orig	2017-10-12 11:46:46 UTC
2
+++ config/action.d/pf.conf
3
@@ -18,8 +18,8 @@
4
 # also, these rulesets are loaded into (nested) anchors
5
 # to enable them, add
6
 #     anchor f2b {
7
-#        name1
8
-#        name2
9
+#        anchor name1
10
+#        anchor name2
11
 #        ...
12
 #     }
13
 # to your main pf ruleset, where "namei" are the names of the jails
14
@@ -110,5 +110,5 @@ allports = any
15
 # Option: multiport
16
 # Notes.: addition to block access only to specific ports
17
 # Usage.: use in jail config: "banaction = pf[actiontype=<multiport>]"
18
-multiport = any port <port>
19
+multiport = any port {<port>}
20
 
(-)pkg-message (-4 / +4 lines)
Lines 12-20 Link Here
12
If you have custom filters or actions and you are upgrading from
12
If you have custom filters or actions and you are upgrading from
13
0.9.x please check them.
13
0.9.x please check them.
14
14
15
Users of pf: please note that instead of 
15
Users of pf: please read the notes in action.d/pf.conf and the
16
action = pf
16
discussion at https://github.com/fail2ban/fail2ban/pull/1925
17
you hae to write someting like
17
Please note that fail2ban will put curly braces '{}' around the
18
action = pf[port={80 443}, name=http]
18
ports in the action so you shouldn't do it yourself.
19
19
20
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
20
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Return to bug 223069