Skip to content
This repository

Daemon to ban hosts that cause multiple authentication errors

branch: master
Octocat-spinner-32 bin Add a --print-all-matched option. March 17, 2014
Octocat-spinner-32 config DOC: minor -- tabify docstring in action April 23, 2014
Octocat-spinner-32 doc DOC: sphinx documentation March 29, 2014
Octocat-spinner-32 fail2ban DOC: Add notice message for systemd backend when no journal match April 20, 2014
Octocat-spinner-32 files Create fail2ban.upstart April 11, 2014
Octocat-spinner-32 man DOC: Fix jail.conf(5) man page which had duplicate {fail,ignore}regex April 03, 2014
Octocat-spinner-32 .coveragerc TST+BF: Use separate coveragerc for Travis CI March 29, 2013
Octocat-spinner-32 .gitignore MRG: from master again 2014-01-01 January 01, 2014
Octocat-spinner-32 .project - Added Eclipse project file October 17, 2006
Octocat-spinner-32 .pydevproject - Removed Python 2.4. Minimum required version is now Python 2.3. December 16, 2007
Octocat-spinner-32 .pylintrc ENH: added a .pylintrc to help with consistent appearance and catch o… October 04, 2011
Octocat-spinner-32 .travis.yml Revert "TST: Add Python 3.4 for TravisCI" April 19, 2014
Octocat-spinner-32 .travis_coveragerc TST: TravisCI coverage now includes untested systemd backend elements May 13, 2013
Octocat-spinner-32 DOC: minor -- added a link to pull requests in CONTRIBUTING April 17, 2014
Octocat-spinner-32 COPYING - Added ISO 8601 date/time format. May 18, 2008
Octocat-spinner-32 ChangeLog BF: recidive filter and samples at wrong log level: WARNING->NOTICE April 19, 2014
Octocat-spinner-32 DEVELOP DOC: sphinx documentation March 29, 2014
Octocat-spinner-32 FILTERS DOC: sphinx documentation March 29, 2014
Octocat-spinner-32 MANIFEST Merge commit '0.8.13-1-ga8d0cc9' March 17, 2014
Octocat-spinner-32 PKG: Add RELEASE and March 15, 2014
Octocat-spinner-32 README.Solaris DOC: minor changes just to trigger the build April 17, 2014
Octocat-spinner-32 ENH(DOC): Move contributions related docs into so it … April 17, 2014
Octocat-spinner-32 RELEASE DOC: sphinx documentation March 29, 2014
Octocat-spinner-32 THANKS DOC: add thanks for last commit April 03, 2014
Octocat-spinner-32 TODO DOC: deadlock resolved with locking introduced in 3a58d0e and d07df66 March 15, 2014
Octocat-spinner-32 fail2ban-2to3 TST: Fix up fail2ban python3 scripts April 13, 2013
Octocat-spinner-32 fail2ban-testcases-all ENH+TST: Move fail2ban-* scripts to bin/ April 01, 2013
Octocat-spinner-32 fail2ban-testcases-all-python3 TST: Fix up fail2ban python3 scripts April 13, 2013
Octocat-spinner-32 kill-server - Initial commit of the new development release 0.7 June 26, 2006
Octocat-spinner-32 setup.cfg Merge branch 'master' into 0.9 May 02, 2013
Octocat-spinner-32 Clean up April 04, 2014
                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   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


Bugs, feature requests, discussions?


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.