Skip to content
This repository

Daemon to ban hosts that cause multiple authentication errors

branch: master

Merge pull request #683 from yarikoptic/fix/682

Fix typos referencing  paths-common, provide empty defaults for syslog_ log files (Partial fix to #682)
latest commit d4427e5a76
Steven Hiscocks kwirk authored
Octocat-spinner-32 bin Add a --print-all-matched option.
Octocat-spinner-32 config Merge pull request #683 from yarikoptic/fix/682
Octocat-spinner-32 doc DOC: sphinx documentation
Octocat-spinner-32 fail2ban ENH: Log trace info for failed action events when in DEBUG
Octocat-spinner-32 files Create fail2ban.upstart
Octocat-spinner-32 man DOC: Fix jail.conf(5) man page which had duplicate {fail,ignore}regex
Octocat-spinner-32 .coveragerc TST+BF: Use separate coveragerc for Travis CI
Octocat-spinner-32 .gitignore MRG: from master again 2014-01-01
Octocat-spinner-32 .project - Added Eclipse project file
Octocat-spinner-32 .pydevproject - Removed Python 2.4. Minimum required version is now Python 2.3.
Octocat-spinner-32 .pylintrc ENH: added a .pylintrc to help with consistent appearance and catch o…
Octocat-spinner-32 .travis.yml MRG: from master to 0.9 2014-02-20
Octocat-spinner-32 .travis_coveragerc TST: TravisCI coverage now includes untested systemd backend elements
Octocat-spinner-32 COPYING - Added ISO 8601 date/time format.
Octocat-spinner-32 ChangeLog DOC: Update ChangeLog
Octocat-spinner-32 DEVELOP DOC: sphinx documentation
Octocat-spinner-32 FILTERS DOC: sphinx documentation
Octocat-spinner-32 MANIFEST Merge commit '0.8.13-1-ga8d0cc9'
Octocat-spinner-32 PKG: Add RELEASE and
Octocat-spinner-32 README.Solaris DOC: fix ChangeLog merge
Octocat-spinner-32 DOC: versioning and release/readme notes
Octocat-spinner-32 RELEASE DOC: sphinx documentation
Octocat-spinner-32 THANKS DOC: add thanks for last commit
Octocat-spinner-32 TODO DOC: deadlock resolved with locking introduced in 3a58d0e and d07df66
Octocat-spinner-32 fail2ban-2to3 TST: Fix up fail2ban python3 scripts
Octocat-spinner-32 fail2ban-testcases-all ENH+TST: Move fail2ban-* scripts to bin/
Octocat-spinner-32 fail2ban-testcases-all-python3 TST: Fix up fail2ban python3 scripts
Octocat-spinner-32 kill-server - Initial commit of the new development release 0.7
Octocat-spinner-32 setup.cfg Merge branch 'master' into 0.9
Octocat-spinner-32 Clean up
                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.9.0                  2014/03/14

Fail2Ban: ban hosts that cause multiple authentication errors

Fail2Ban scans log files like /var/log/pwdfail and bans IP that makes too many password failures. It updates firewall rules to reject the IP address. These rules can be defined by the user. Fail2Ban can read multiple log files such as sshd or Apache web server ones.

Fail2Ban is able to reduce the rate of incorrect authentications attempts however it cannot eliminate the risk that weak authentication presents. Configure services to use only two factor or public/private authentication mechanisms if you really want to protect services.

This README is a quick introduction to Fail2ban. More documentation, FAQ, HOWTOs are available in fail2ban(1) manpage and on the website


It is possible that Fail2ban is already packaged for your distribution. In this case, you should use it instead.



To install, just do:

tar xvfj fail2ban-0.9.0.tar.bz2
cd fail2ban-0.9.0
python install

This will install Fail2Ban into the python library directory. The executable scripts are placed into /usr/bin, and configuration under /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 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:

  • tests status (master branch)

  • Coverage Status


You found a severe security vulnerability in Fail2Ban?

email details to fail2ban-vulnerabilities at lists dot sourceforge dot net .

You need some new features, you found bugs?

visit Issues and if your issue is not yet known -- file a bug report. See Fail2Ban wiki on further instructions.

You would like to troubleshoot or discuss?

join the mailing list

You would like to contribute (new filters/actions/code/documentation)?

send a pull request

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.


See THANKS file.


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

Something went wrong with that request. Please try again.