Go to file
Daniel Black eaba732d5b Merge pull request #370 from grooverdan/test
MRG: more unit tests
2013-09-29 00:41:33 -07:00
client Change /tmp/fail2ban.sock to /var/run/fail2ban/fail2ban.sock 2013-08-08 20:28:55 -06:00
common ENH: simplify our formatExceptionInfo 2013-09-12 22:47:58 -04:00
config MRG/DOC: jail.conf resolution, ChangeLog fixes 2013-09-29 08:21:13 +10:00
doc Fixed typos 2013-03-10 22:05:33 +00:00
files Merge pull request #240 from jpmx/master 2013-08-31 06:57:42 -07:00
man Changes for 0.8.10 release (changelog, version, etc) 2013-06-11 19:20:50 -04:00
server BF: simplify 2013-09-29 15:49:45 +10:00
testcases TST: dummyjail in own class 2013-09-29 15:57:03 +10: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: Coverage for coveralls.io should only be run on success 2013-04-14 15:56:14 +01: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 MRG/DOC: jail.conf resolution, ChangeLog fixes 2013-09-29 08:21:13 +10:00
DEVELOP DOC: additional pass over DEVELOP (just rephrasings, spaces, formatting) 2013-09-25 22:12:36 -04:00
MANIFEST ENH: Change lighttpd-fastcgi to suhosin, and improve regex and samples 2013-07-21 16:35:37 +01:00
README.Solaris DOC: fix ChangeLog merge 2013-07-28 18:02:38 +10:00
README.md DOC: add information on where to report vulnerabilities + pointer to HOWTO_Seek_Help 2013-06-12 13:21:12 -04:00
THANKS add ChangeLog and THANKS entry 2013-09-25 18:04:05 -04:00
TODO added new date format support for ASSP SMTP Proxy 2013-05-03 00:56:46 -04:00
fail2ban-client BF: catch and report exceptions while executing commands in client interactive mode (Close #353) 2013-09-15 23:05:32 -04:00
fail2ban-regex ENH: fail2ban-regex now uses iteraable for log file 2013-07-27 11:36:01 +01:00
fail2ban-server ENH: deleted trailing spaces in fail2ban- cmdline tools 2013-03-29 12:31:50 -04:00
fail2ban-testcases TST: add test cases for Actions 2013-09-29 14:52:59 +10:00
fail2ban-testcases-all ENH: fail2ban-testcases-all -- pass cmdline options to fail2ban-testcases 2012-11-07 11:34:20 -05:00
kill-server - Initial commit of the new development release 0.7 2006-06-26 20:05:00 +00:00
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.10                  2013/06/12

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.10.tar.bz2
cd fail2ban-0.8.10
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