Daemon to ban hosts that cause multiple authentication errors
Python Shell Perl ApacheConf
Latest commit a0d8581 Sep 26, 2016 @sebres sebres committed on GitHub Merge pull request #1557 from sebres/_0.10/fix-reload-bug
 0.10/reload-and-more: reload without restart, stability and performance fixes
Permalink
Failed to load latest commit information.
.github DOC: added a note about choose correct branch for PR Jul 15, 2016
bin simplify fail2ban-testcases: move some code pieces inclusive option p… Aug 18, 2016
config Merge remote-tracking branch 'remotes/gh-upstream/master' into 0.10 Sep 1, 2016
doc - performance of fail2ban optimized Dec 29, 2015
fail2ban extended test-cases (coverage) Sep 26, 2016
files fixed --pidfile bug, introduced in gh-1322: May 20, 2016
man switch down log level for some annoying messages to tracedebug or hea… Sep 22, 2016
.coveragerc Consolidate coveragerc configs into .coveragerc (delete .travis_cover… Jul 9, 2015
.gitignore Add .idea dir to .gitignore Dec 30, 2014
.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 new test-cases option "--verbosity" to set numeric level of verbosity… Aug 17, 2016
CONTRIBUTING.md Added to CONTRIBUTING.md minimal guidelines for PRs Feb 4, 2015
COPYING - Added ISO 8601 date/time format. May 18, 2008
ChangeLog ChangeLog entries added Sep 26, 2016
DEVELOP DOC: Use coverage report and optionally coverage html Jul 9, 2015
FILTERS DOC: sphinx documentation Mar 29, 2014
MANIFEST compatibility fix (virtualenv, running test cases in py3) Aug 11, 2016
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 Aug 16, 2016
RELEASE Merge branch 'master' into 0.10 Aug 1, 2016
THANKS Update ChangeLog / THANKS entries May 9, 2016
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 TST: Fix up fail2ban python3 scripts Apr 13, 2013
fail2ban-testcases-all ENH+TST: Move fail2ban-* scripts to bin/ Apr 1, 2013
fail2ban-testcases-all-python3 TST: Fix up fail2ban python3 scripts Apr 13, 2013
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 amend to 2e530fc: setuptools compatibility fix - just to be sure if i… Aug 12, 2016

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.10.0                 2016/??/??

Fail2Ban: ban hosts that cause multiple authentication errors

Fail2Ban scans log files like /var/log/auth.log and bans IP addresses having 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 easy to configure to read any log file you choose, for any error you choose.

Though Fail2Ban is able to reduce the rate of incorrect authentications attempts, 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 http://www.fail2ban.org

Installation:

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

Required:

Optional:

To install, just do:

tar xvfj fail2ban-0.10.0.tar.bz2
cd fail2ban-0.10.0
python setup.py 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.

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:

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

  • Coverage Status

  • codecov.io

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