Na}{

File Content: `cloudflare-token.conf`

#
# Author: Logic-32
#
# IMPORTANT
#
# Please set jail.local's permission to 640 because it contains your CF API token.
#
# This action depends on curl.
#
# To get your Cloudflare API token: https://developers.cloudflare.com/api/tokens/create/
#
# Cloudflare Firewall API: https://developers.cloudflare.com/firewall/api/cf-firewall-rules/endpoints/

[Definition]

# Option:  actionstart
# Notes.:  command executed on demand at the first ban (or at the start of Fail2Ban if actionstart_on_demand is set to false).
# Values:  CMD
#
actionstart =

# Option:  actionstop
# Notes.:  command executed at the stop of jail (or at the end of Fail2Ban)
# Values:  CMD
#
actionstop =

# Option:  actioncheck
# Notes.:  command executed once before each actionban command
# Values:  CMD
#
actioncheck =

# Option:  actionban
# Notes.:  command executed when banning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:    <ip>  IP address
#          <failures>  number of failures
#          <time>  unix timestamp of the ban time
# Values:  CMD
actionban = curl -s -X POST "<_cf_api_url>" \
              <_cf_api_prms> \
              --data '{"mode":"<cfmode>","configuration":{"target":"<cftarget>","value":"<ip>"},"notes":"<notes>"}'

# Option:  actionunban
# Notes.:  command executed when unbanning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:    <ip>  IP address
#          <failures>  number of failures
#          <time>  unix timestamp of the ban time
# Values:  CMD
#
actionunban = id=$(curl -s -X GET "<_cf_api_url>" \
              --data-urlencode "mode=<cfmode>" --data-urlencode "notes=<notes>" --data-urlencode "configuration.target=<cftarget>" --data-urlencode "configuration.value=<ip>" \
              <_cf_api_prms> \
                  | awk -F"[,:}]" '{for(i=1;i<=NF;i++){if($i~/'id'\042/){print $(i+1)}}}' \
                  | tr -d ' "' \
                  | head -n 1)
              if [ -z "$id" ]; then echo "<name>: id for <ip> cannot be found using target <cftarget>"; exit 0; fi; \
              curl -s -X DELETE "<_cf_api_url>/$id" \
                  <_cf_api_prms> \
                  --data '{"cascade": "none"}'

_cf_api_url = https://api.cloudflare.com/client/v4/zones/<cfzone>/firewall/access_rules/rules
_cf_api_prms = -H "Authorization: Bearer <cftoken>" -H "Content-Type: application/json"

[Init]

# Declare your Cloudflare Authorization Bearer Token in the [DEFAULT] section of your jail.local file.

# The Cloudflare <ZONE_ID> of the domain you want to manage.
#
# cfzone =

# Your personal Cloudflare token.  Ideally restricted to just have "Zone.Firewall Services" permissions.
#
# cftoken =

# Target of the firewall rule.  Default is "ip" (v4).
#
cftarget = ip

# The firewall mode Cloudflare should use.  Default is "block" (deny access).
# Consider also "js_challenge" or other "allowed_modes" if you want.
#
cfmode = block

# The message to include in the firewall IP banning rule.
#
notes = Fail2Ban <name>

[Init?family=inet6]
cftarget = ip6

Name	Size	Permission
abuseipdb.conf	3748 bytes	0644
apf.conf	587 bytes	0644
apprise.conf	1413 bytes	0644
blocklist_de.conf	2715 bytes	0644
bsd-ipfw.conf	3226 bytes	0644
cloudflare-token.conf	3072 bytes	0644
cloudflare.conf	3037 bytes	0644
complain.conf	4773 bytes	0644
dshield.conf	7684 bytes	0644
dummy.conf	1717 bytes	0644
firewallcmd-allports.conf	1501 bytes	0644
firewallcmd-common.conf	2649 bytes	0644
firewallcmd-ipset.conf	3928 bytes	0644
firewallcmd-multiport.conf	1270 bytes	0644
firewallcmd-new.conf	1898 bytes	0644
firewallcmd-rich-logging.conf	1021 bytes	0644
firewallcmd-rich-rules.conf	1753 bytes	0644
helpers-common.conf	592 bytes	0644
hostsdeny.conf	1657 bytes	0644
ipfilter.conf	1573 bytes	0644
ipfw.conf	1505 bytes	0644
iptables-allports.conf	291 bytes	0644
iptables-ipset-proto4.conf	2221 bytes	0644
iptables-ipset-proto6-allports.conf	814 bytes	0644
iptables-ipset-proto6.conf	773 bytes	0644
iptables-ipset.conf	2810 bytes	0644
iptables-multiport-log.conf	2163 bytes	0644
iptables-multiport.conf	232 bytes	0644
iptables-new.conf	332 bytes	0644
iptables-xt_recent-echo.conf	2842 bytes	0644
iptables.conf	4791 bytes	0644
ipthreat.conf	4291 bytes	0644
mail-buffered.conf	2495 bytes	0644
mail-whois-common.conf	1051 bytes	0644
mail-whois-lines.conf	2459 bytes	0644
mail-whois.conf	1890 bytes	0644
mail.conf	1757 bytes	0644
mikrotik.conf	2546 bytes	0644
mynetwatchman.conf	5321 bytes	0644
netscaler.conf	1493 bytes	0644
nftables-allports.conf	383 bytes	0644
nftables-multiport.conf	384 bytes	0644
nftables.conf	6317 bytes	0644
nginx-block-map.conf	4010 bytes	0644
npf.conf	1524 bytes	0644
nsupdate.conf	3234 bytes	0644
osx-afctl.conf	497 bytes	0644
osx-ipfw.conf	2302 bytes	0644
pf.conf	4082 bytes	0644
route.conf	1023 bytes	0644
sendmail-buffered.conf	2806 bytes	0644
sendmail-common.conf	1939 bytes	0644
sendmail-geoip-lines.conf	1761 bytes	0644
sendmail-whois-ipjailmatches.conf	1055 bytes	0644
sendmail-whois-ipmatches.conf	1036 bytes	0644
sendmail-whois-lines.conf	1299 bytes	0644
sendmail-whois-matches.conf	1000 bytes	0644
sendmail-whois.conf	950 bytes	0644
sendmail.conf	829 bytes	0644
shorewall-ipset-proto6.conf	3762 bytes	0644
shorewall.conf	2156 bytes	0644
smtp.py	6655 bytes	0644
symbiosis-blacklist-allports.conf	1503 bytes	0644
ufw.conf	2379 bytes	0644
xarf-login-attack.conf	6443 bytes	0644

File Content: cloudflare-token.conf

File Content: `cloudflare-token.conf`