fail2ban/config/action.d/cloudflare.conf

84 lines
2.8 KiB
Plaintext
Raw Normal View History

2014-07-18 02:54:30 +00:00
#
# Author: Mike Rushton
#
2015-07-01 07:38:36 +00:00
# IMPORTANT
2014-07-18 03:49:35 +00:00
#
2015-07-01 07:38:36 +00:00
# Please set jail.local's permission to 640 because it contains your CF API key.
2014-07-18 02:54:30 +00:00
#
# This action depends on curl and jq.
2015-07-01 07:38:36 +00:00
# Referenced from http://www.normyee.net/blog/2012/02/02/adding-cloudflare-support-to-fail2ban by NORM YEE
#
# To get your CloudFlare API Key: https://www.cloudflare.com/a/account/my-account
2015-09-30 14:07:45 +00:00
#
# CloudFlare API error codes: https://www.cloudflare.com/docs/host-api.html#s4.2
2014-07-18 02:54:30 +00:00
[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).
2014-07-18 02:54:30 +00:00
# Values: CMD
#
actionstart =
# Option: actionstop
# Notes.: command executed at the stop of jail (or at the end of Fail2Ban)
2014-07-18 02:54:30 +00:00
# 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.
2014-07-18 03:49:35 +00:00
# Tags: <ip> IP address
# <failures> number of failures
# <time> unix timestamp of the ban time
2014-07-18 02:54:30 +00:00
# Values: CMD
#
# API v1
#actionban = curl -s -o /dev/null https://www.cloudflare.com/api_json.html -d 'a=ban' -d 'tkn=<cftoken>' -d 'email=<cfuser>' -d 'key=<ip>'
# API v4
actionban = curl -s -o /dev/null -X POST <_cf_api_prms> \
-d '{"mode":"block","configuration":{"target":"ip","value":"<ip>"},"notes":"Fail2Ban <name>"}' \
<_cf_api_url>
2015-07-01 07:38:36 +00:00
2014-07-18 02:54:30 +00:00
# Option: actionunban
# Notes.: command executed when unbanning an IP. Take care that the
# command is executed with Fail2Ban user rights.
2014-07-18 03:49:35 +00:00
# Tags: <ip> IP address
# <failures> number of failures
# <time> unix timestamp of the ban time
2014-07-18 02:54:30 +00:00
# Values: CMD
#
# API v1
#actionunban = curl -s -o /dev/null https://www.cloudflare.com/api_json.html -d 'a=nul' -d 'tkn=<cftoken>' -d 'email=<cfuser>' -d 'key=<ip>'
# API v4
actionunban = id=$(curl -s -X GET <_cf_api_prms> \
2018-12-10 10:27:53 +00:00
"<_cf_api_url>?mode=block&configuration_target=ip&configuration_value=<ip>&page=1&per_page=1&notes=Fail2Ban%%20<name>" \
| jq -r '.result[0].id')
if [ -z "$id" ]; then echo "<name>: id for <ip> cannot be found"; exit 0; fi;
curl -s -o /dev/null -X DELETE <_cf_api_prms> "<_cf_api_url>/$id"
_cf_api_url = https://api.cloudflare.com/client/v4/user/firewall/access_rules/rules
2018-12-10 10:27:53 +00:00
_cf_api_prms = -H 'X-Auth-Email: <cfuser>' -H 'X-Auth-Key: <cftoken>' -H 'Content-Type: application/json'
2014-07-18 02:54:30 +00:00
[Init]
# If you like to use this action with mailing whois lines, you could use the composite action
# action_cf_mwl predefined in jail.conf, just define in your jail:
#
# action = %(action_cf_mwl)s
# # Your CF account e-mail
# cfemail =
# # Your CF API Key
# cfapikey =
cftoken =
cfuser =