You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Go to file
Daniel Black dab2ddb9da
ENH: recidive jail to block all protocols. Closes #440
11 years ago
client ENH: order config as jail.conf, jail.d/*.conf, jail.local, jail.d/*.local. closes gh-388 11 years ago
common DOC: post release version change 11 years ago
config ENH: recidive jail to block all protocols. Closes #440 11 years ago
doc Fixed typos 12 years ago
files NF: gen_badbots script to (re)generate/update config/filter.d/apache-badbots.conf 11 years ago
man DOC: finalise 0.8.11 release 11 years ago
server ENH: adding custom date format for proftpd when logging in its own log file (default on Debian) -- includes milliseconds 11 years ago
testcases ENH: adding custom date format for proftpd when logging in its own log file (default on Debian) -- includes milliseconds 11 years ago
.coveragerc TST+BF: Use separate coveragerc for Travis CI 12 years ago
.gitignore ENH: git ignore failed patch reminants 12 years ago
.project - Added Eclipse project file 18 years ago
.pydevproject - Removed Python 2.4. Minimum required version is now Python 2.3. 17 years ago
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch obvious problems 13 years ago
.travis.yml TST: Coverage for coveralls.io should only be run on success 12 years ago
.travis_coveragerc TST: Add gamin support for Travis CI 12 years ago
COPYING - Added ISO 8601 date/time format. 17 years ago
ChangeLog ENH: recidive jail to block all protocols. Closes #440 11 years ago
DEVELOP DOC: list Wiki pages to update after a release 11 years ago
MANIFEST DOC: finalise 0.8.11 release 11 years ago
README.Solaris DOC: fix ChangeLog merge 12 years ago
README.md DOC: finalise 0.8.11 release 11 years ago
THANKS BF/ENH: asterisk connection ID is a hex not decimal number. Add "Rejecting unknown SIP connection from <HOST>" regex thanks to Jonathan Lanning 11 years ago
TODO added new date format support for ASSP SMTP Proxy 12 years ago
fail2ban-client BF: log errors to syslog and respect the showRet parameter 11 years ago
fail2ban-regex ENH: fix fail2ban-regex output to generate a man page with copyright notices 11 years ago
fail2ban-server ENH: deleted trailing spaces in fail2ban- cmdline tools 12 years ago
fail2ban-testcases TST: add test cases for Actions 11 years ago
fail2ban-testcases-all ENH: fail2ban-testcases-all -- pass cmdline options to fail2ban-testcases 12 years ago
kill-server - Initial commit of the new development release 0.7 19 years ago
setup.cfg BF: Rename mentioning of README to README.md (Fixes #187) 12 years ago
setup.py Install empty /etc/fail2ban/fail2ban.d directory 11 years ago

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