fail2ban: Update AbuseIPDB actionban script instructions

- Clarified integration steps for placing the script in 'action.d'
- Updated example configuration with correct script name 'fail2ban-abuseipdb.sh'
- Emphasized the need to set 'abuseipdb_apikey' in the config file
- Improved formatting and readability for better user understanding

No functional changes, just documentation updates.
pull/3948/head
Hasan ÇALIŞIR 2025-02-22 22:27:40 +03:00 committed by GitHub
parent b468593e93
commit b423631825
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions

View File

@ -8,13 +8,13 @@
# been reported previously, thereby avoiding redundant entries and potential API rate limiting.
#
# Integration with Fail2Ban:
# - Place this script in the Fail2Ban `action.d` directory named 'abuseipdb_fail2ban_actionban.sh'
# - Configure Fail2Ban to use this script as the `actionban` for relevant jails.
# - Place this script in the 'action.d' directory of Fail2Ban.
# - Configure Fail2Ban to use this script as the `actionban`.
# - First edit 'abuseipdb.conf' in '/etc/fail2ban/action.d/abuseipdb.conf' and add following rule,
# - actionban = /etc/fail2ban/action.d/abuseipdb_fail2ban_actionban.sh \
# - actionban = /etc/fail2ban/action.d/fail2ban-abuseipdb.sh \
# "<abuseipdb_apikey>" "<matches>" "<ip>" "<abuseipdb_category>" "<bantime>"
# - Also make sure you set your 'abuseipdb_apikey' in the configuration file.
# - Final step, adjust your jails accordingly. Check the below jail example to also reporting with custom comment via 'tp_comment'
# - Adjust your jails accordingly. Check the below jail example to also reporting with custom comment via 'tp_comment'
#
# Example jail in 'jail.local':
# [nginx-botsearch]