Go to file
Hasan ÇALIŞIR 00bb41b864
refactor AbuseIPDB integration with improved concurrency and error handling
This refactors the AbuseIPDB integration for Fail2Ban with major improvements:
- Introduced separate lock files (LOCK_INIT, LOCK_BAN, LOCK_DONE) to better handle concurrent
  initialization and prevent race conditions during restarts.
- LOCK_BAN → serializes ban reports to the API (during actionban).
- LOCK_DONE → can signal completion or be used for future synchronization (like restart-safe exits).
- LOCK_INIT with flock in actionstart to prevent concurrent
  initialization, ensuring SQLite and log file integrity during parallel
  Fail2Ban restarts or multiple jail startups.
- Enhanced argument validation for both actionstart and actionban to prevent silent failures.
- Improved database initialization checks, ensuring proper creation of directories and log files.
- Added persistent SQLite pragmas for performance optimization under concurrent access.
- Refined error handling and logging for API interactions, including better detection of
  rate-limiting (HTTP 429) and invalid responses.
- Implemented consistent whitespace trimming and sanitization on IP addresses and bantime inputs.
- Improved modularity with dedicated helper functions, reducing code duplication and improving
  maintainability.
- Ensured background execution with better log redirection and failure tracking.
- Verify local DB insertions, aborting the process on failure to prevent
  incomplete or invalid state.
- Roll back local DB entries if AbuseIPDB reporting fails, ensuring no
  orphaned records remain.
- Replace basic info logs with clear status and error messages to improve
  traceability and debugging.
- Maintain high integrity between the local database and AbuseIPDB by
  only proceeding when all previous steps succeed.
- Shift from a "continue regardless" flow to a controlled stop on any
  critical error, ensuring system reliability.

Previously, the script assumed success of key steps, risking stale database
entries, silent API call failures, and duplicate reports after Fail2Ban
restarts. These changes improve reliability, prevent data corruption under
high concurrency, and ensure accurate synchronization between local db and
AbuseIPDB API.
2025-03-05 20:04:46 +03:00
.github Update PULL_REQUEST_TEMPLATE.md 2025-03-04 19:19:57 +01:00
bin 2to3 2023-06-16 15:23:41 +02:00
config Merge pull request #3954 from luckylittle/feature/systemd-journal-vsftpd 2025-03-04 14:20:01 +01:00
doc replace distutils for python 3.12 2024-04-27 10:24:01 -07:00
fail2ban test-suite: if failed, sample regexs factory would show responsible header line (failJSON) together with the error line 2025-03-04 14:39:24 +01:00
files refactor AbuseIPDB integration with improved concurrency and error handling 2025-03-05 20:04:46 +03:00
man man extended (`ignoreip` supports file://path/file-with-ip-set) 2025-03-03 19:19:21 +01:00
.codespellrc silence codespell 2025-01-29 21:59:35 +01:00
.coveragerc coverage 2018-07-04 20:16:11 +02:00
.gitattributes Revert "highlighting got broken, so comment out unless GH/linguist gets fixed" 2022-02-22 18:19:44 +01:00
.gitignore Update .gitignore 2023-02-18 23:49:28 +01:00
.mailmap ENH: .mailmap file to bring some names together for git shortlog -sn 2015-11-01 11:28:58 -05:00
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch obvious problems 2011-10-04 10:55:16 -04:00
.typos.toml Remove false positive in logs 2023-11-22 17:14:57 +00:00
CONTRIBUTING.md Added to CONTRIBUTING.md minimal guidelines for PRs 2015-02-03 20:14:53 -05:00
COPYING - Added ISO 8601 date/time format. 2008-05-18 19:53:18 +00:00
ChangeLog Merge pull request #3954 from luckylittle/feature/systemd-journal-vsftpd 2025-03-04 14:20:01 +01:00
DEVELOP Update information reg. ipdns.py as successor for dnsutils.py 2018-12-19 12:17:44 +01:00
FILTERS small amend 2025-01-31 19:54:24 +01:00
MANIFEST preparing release 2024-04-25 22:43:51 +02:00
MANIFEST.in Add ignorecommands to MANIFEST*'s 2015-02-02 15:03:44 -05:00
README.Solaris DOC: minor changes just to trigger the build 2014-04-17 14:34:26 -04:00
README.md README.md: typos 2024-05-14 11:46:49 +02:00
RELEASE Update Arch Linux package URL in RELEASE 2023-11-21 23:05:54 +08:00
THANKS added pf[protocol=all] options as recommended by sebres 2023-12-10 11:20:39 +01:00
TODO DOC: deadlock resolved with locking introduced in 3a58d0e and d07df66 now uses subprocess.Popen. 2014-03-15 09:38:20 +11:00
Vagrantfile Vagrant with two Ubuntu Trusty64 boxes 2014-07-18 17:51:06 +02:00
fail2ban-testcases-all ENH+TST: Move fail2ban-* scripts to bin/ 2013-04-01 19:06:13 +01:00
fail2ban-testcases-all-python3 TST: Fix up fail2ban python3 scripts 2013-04-13 17:01:18 +01:00
kill-server - Initial commit of the new development release 0.7 2006-06-26 20:05:00 +00:00
setup.cfg Merge branch 'master' into 0.9 2013-05-02 23:55:26 -04:00
setup.py setup.py: no distutils anymore 2024-05-07 13:06:50 +02:00

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v1.1.0.dev1            20??/??/??

Fail2Ban: ban hosts that cause multiple authentication errors

Fail2Ban scans log files like /var/log/auth.log and bans IP addresses conducting too many failed login attempts. It does this by updating system firewall rules to reject new connections from those IP addresses, for a configurable amount of time. Fail2Ban comes out-of-the-box ready to read many standard log files, such as those for sshd and Apache, and is easily configured to read any log file of your choosing, for any error you wish.

Though Fail2Ban is able to reduce the rate of incorrect authentication attempts, it cannot eliminate the risk presented by weak authentication. Set up services to use only two factor, or public/private authentication mechanisms if you really want to protect services.

Since v0.10 fail2ban supports the matching of IPv6 addresses.

This README is a quick introduction to Fail2Ban. More documentation, FAQ, and HOWTOs to be found on fail2ban(1) manpage, Wiki, Developers documentation and the website: https://www.fail2ban.org

Installation:

Fail2Ban is likely already packaged for your Linux distribution and can be installed with a simple command.

If your distribution is not listed, you can install from GitHub:

Required:

  • Python >= 3.5 or PyPy3
  • python-setuptools (or python3-setuptools) for installation from source

Optional:

To install:

tar xvfj fail2ban-master.tar.bz2
cd fail2ban-master
sudo python setup.py install

Alternatively, you can clone the source from GitHub to a directory of your choice, and do the install from there. Pick the correct branch, for example, master or 0.11

git clone https://github.com/fail2ban/fail2ban.git
cd fail2ban
sudo python setup.py install 

This will install Fail2Ban into the python library directory. The executable scripts are placed into /usr/bin, and configuration in /etc/fail2ban.

Fail2Ban should be correctly installed now. Just type:

fail2ban-client -h

to see if everything is alright. You should always use fail2ban-client and never call fail2ban-server directly. You can verify that you have the correct version installed with

fail2ban-client version

Please note that the system init/service script is not automatically installed. To enable fail2ban as an automatic service, simply copy the script for your distro from the files directory to /etc/init.d. Example (on a Debian-based system):

cp files/debian-initd /etc/init.d/fail2ban
update-rc.d fail2ban defaults
service fail2ban start

Configuration:

You can configure Fail2Ban using the files in /etc/fail2ban. It is possible to configure the server using commands sent to it by fail2ban-client. The available commands are described in the fail2ban-client(1) manpage. Also see fail2ban(1) and jail.conf(5) manpages for further references.

Code status:

  • CI

Contact:

Bugs, feature requests, discussions?

See CONTRIBUTING.md

You just appreciate this program:

Send kudos to the original author (Cyril Jaquier) or better to the mailing list since Fail2Ban is "community-driven" for years now.

Thanks:

See THANKS file.

License:

Fail2Ban is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

Fail2Ban is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with Fail2Ban; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110, USA