Go to file
Yaroslav Halchenko 0141a6dbe7 TST: add few more rudimentary tests for Regex to complete its coverage 2013-12-27 01:29:02 -05:00
client New ignorecommand that is added to the ignoreip list from output of an external program 2013-12-24 23:55:35 +03:00
common New ignorecommand that is added to the ignoreip list from output of an external program 2013-12-24 23:55:35 +03:00
config TST: include blank ignorecommand in jail.conf to indicate default value and to raise test coverage 2013-12-25 11:01:31 +00:00
doc Fixed typos 2013-03-10 22:05:33 +00:00
files Updated check_fail2ban to return performance data for all jails and applied to specific jail code 2013-12-17 17:48:19 +00:00
man New ignorecommand that is added to the ignoreip list from output of an external program 2013-12-24 23:55:35 +03:00
server New ignorecommand that is added to the ignoreip list from output of an external program 2013-12-24 23:55:35 +03:00
testcases TST: add few more rudimentary tests for Regex to complete its coverage 2013-12-27 01:29:02 -05:00
.coveragerc TST+BF: Use separate coveragerc for Travis CI 2013-03-29 20:14:13 +00:00
.gitignore ENH: git ignore failed patch reminants 2013-03-16 13:53:51 +11: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 TST: no python-2.5 any more - https://github.com/travis-ci/travis-ci/issues/1668 2013-11-25 07:54:49 +11:00
.travis_coveragerc TST: Add gamin support for Travis CI 2013-03-30 18:17:01 +00:00
COPYING - Added ISO 8601 date/time format. 2008-05-18 19:53:18 +00:00
ChangeLog BF: apache-2.4 log format fix. Closes gh-516 2013-12-23 08:28:40 +00:00
DEVELOP DOC: more distro bug tracker urls 2013-11-24 18:43:23 +11:00
MANIFEST BF: Add testcases/files/ignorecommand.py to MANIFEST 2013-12-25 10:55:26 +00:00
README.Solaris DOC: fix ChangeLog merge 2013-07-28 18:02:38 +10:00
README.md DOC: finalise 0.8.11 release 2013-11-13 08:05:08 +11:00
THANKS BF: apache-2.4 log format fix. Closes gh-516 2013-12-23 08:28:40 +00:00
TODO added new date format support for ASSP SMTP Proxy 2013-05-03 00:56:46 -04:00
fail2ban-client BF: log errors to syslog and respect the showRet parameter 2013-10-22 23:25:43 +11:00
fail2ban-regex ENH: fix fail2ban-regex output to generate a man page with copyright notices 2013-10-31 10:26:49 +11:00
fail2ban-server ENH: deleted trailing spaces in fail2ban- cmdline tools 2013-03-29 12:31:50 -04:00
fail2ban-testcases TST: add few more rudimentary tests for Regex to complete its coverage 2013-12-27 01:29:02 -05:00
fail2ban-testcases-all ENH: fail2ban-testcases-all -- pass cmdline options to fail2ban-testcases 2012-11-07 11:34:20 -05:00
kill-server
setup.cfg BF: Rename mentioning of README to README.md (Fixes #187) 2013-04-26 22:51:59 -04:00
setup.py Install empty /etc/fail2ban/fail2ban.d directory 2013-08-28 11:33:05 -06:00

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.8.11                 2013/11/13

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.

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.8.11.tar.bz2
cd fail2ban-0.8.11
python setup.py install

This will install Fail2Ban into /usr/share/fail2ban. 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) manpage for further references and find even more documentation on the website: http://www.fail2ban.org

Code status:

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

  • Coverage Status

Contact:

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](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