Skip to content
Daemon to ban hosts that cause multiple authentication errors
Branch: 0.11
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github DOC: added a note about choose correct branch for PR Jul 15, 2016
bin DOC: minor typos spotted around comments etc Jan 23, 2018
config
doc - performance of fail2ban optimized Dec 29, 2015
fail2ban Merge branch '0.10' into 0.11 Mar 12, 2019
files tmpfiles.d: don't use legacy directory path Mar 13, 2019
man Merge branch '0.10' into 0.11 Mar 1, 2019
.coveragerc
.gitignore
.mailmap ENH: .mailmap file to bring some names together for git shortlog -sn Nov 1, 2015
.project - Added Eclipse project file Oct 17, 2006
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch o… Oct 4, 2011
.travis.yml
CONTRIBUTING.md Added to CONTRIBUTING.md minimal guidelines for PRs Feb 4, 2015
COPYING
ChangeLog Merge branch '0.10' into 0.11 Mar 1, 2019
DEVELOP Update information reg. ipdns.py as successor for dnsutils.py Dec 19, 2018
FILTERS
MANIFEST Merge branch '0.10' into 0.11 (conflicts resolved, tests fixed) Feb 21, 2019
MANIFEST.in Add ignorecommands to MANIFEST*'s Feb 2, 2015
README.Solaris DOC: minor changes just to trigger the build Apr 17, 2014
README.md Update README.md Nov 26, 2018
RELEASE
THANKS
TODO DOC: deadlock resolved with locking introduced in 3a58d0e and d07df66 Mar 14, 2014
Vagrantfile Vagrant with two Ubuntu Trusty64 boxes Jul 18, 2014
fail2ban-2to3
fail2ban-testcases-all ENH+TST: Move fail2ban-* scripts to bin/ Apr 1, 2013
fail2ban-testcases-all-python3
kill-server - Initial commit of the new development release 0.7 Jun 26, 2006
setup.cfg Merge branch 'master' into 0.9 May 3, 2013
setup.py minor amend for better readability Dec 17, 2018

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.11.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:

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

Required:

Optional:

To install:

tar xvfj fail2ban-0.11.0.tar.bz2
cd fail2ban-0.11.0
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, 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:

  • travis-ci.org: tests status (0.11 branch) / tests status (0.10 branch)

  • coveralls.io: Coverage Status (0.11 branch) / Coverage Status / (0.10 branch)

  • codecov.io: codecov.io (0.11 branch) / codecov.io (0.10 branch)

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

You can’t perform that action at this time.