Go to file
sebres 286ef6aa87 code review 2014-10-26 22:14:57 +01:00
bin ENH: do use @staticmethod (we are well beyond support of 2.4 now) 2014-10-25 09:25:18 -04:00
config Merge remote-tracking branch 'remotes/upstream/master' into sebres:ban-time-incr; 2014-10-25 19:05:53 +02:00
doc DOC: sphinx documentation 2014-03-29 22:07:33 +00:00
fail2ban code review 2014-10-26 22:14:57 +01:00
files RF: moving logwatch setup/sample logs under files/logwatch 2014-09-14 09:48:14 -04:00
man ENH: Add version command to protocol 2014-07-15 06:19:13 +00:00
.coveragerc TST+BF: Use separate coveragerc for Travis CI 2013-03-29 20:14:13 +00:00
.gitignore Adding vagrant support 2014-07-17 16:44:45 +02:00
.project - Added Eclipse project file 2006-10-17 21:24:27 +00:00
.pydevproject - Removed Python 2.4. Minimum required version is now Python 2.3. 2007-12-16 21:38:04 +00:00
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch obvious problems 2011-10-04 10:55:16 -04:00
.travis.yml We better check that installation doesn't cause any errors as well 2014-10-12 17:28:35 -04:00
.travis_coveragerc TST: TravisCI coverage now includes untested systemd backend elements 2013-05-13 23:44:01 +01:00
CONTRIBUTING.md DOC: minor -- added a link to pull requests in CONTRIBUTING 2014-04-17 23:16:41 -04:00
COPYING - Added ISO 8601 date/time format. 2008-05-18 19:53:18 +00:00
ChangeLog Merge remote-tracking branch 'remotes/upstream/master' into sebres:ban-time-incr; 2014-10-25 19:05:53 +02:00
DEVELOP DOC: documentation about available vagrantfile setup 2014-10-25 10:38:18 -04:00
FILTERS DOC: sphinx documentation 2014-03-29 22:07:33 +00:00
MANIFEST ENH: Introduce iptables-common.conf. 2014-06-18 19:04:57 +09:00
MANIFEST.in PKG: Add RELEASE and MANIFEST.in 2014-03-15 18:45:49 +11:00
README.Solaris DOC: minor changes just to trigger the build 2014-04-17 14:34:26 -04:00
README.md ENH(DOC): Move contributions related docs into CONTRIBUTING.md so it pops up when people file PR/issues 2014-04-17 13:19:03 -04:00
RELEASE DOC: sphinx documentation 2014-03-29 22:07:33 +00:00
THANKS Merge remote-tracking branch 'remotes/upstream/master' into sebres:ban-time-incr; 2014-10-25 19:05:53 +02: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-2to3 TST: Fix up fail2ban python3 scripts 2013-04-13 17:01:18 +01: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 Clean up setup.py 2014-04-04 02:54:53 +00:00

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   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 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.9.0.tar.bz2
cd fail2ban-0.9.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.

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 (master branch)

  • Coverage Status

Contact:

Bugs, feature requests, discussions?

See CONTRIBUTING.md

You just appreciate this program:

send kudos to the original author ([Cyril Jaquier](mailto: Cyril Jaquier cyril.jaquier@fail2ban.org)) 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