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 cc463aa60d
Merge pull request #620 from kwirk/xarf-tweaks
11 years ago
bin Merge branch 'master' into 0.9 11 years ago
config Merge pull request #620 from kwirk/xarf-tweaks 11 years ago
doc ENH: Add root user check in xt_recent, and add missing actionstop 11 years ago
fail2ban MRG: from master to 0.9 2014-02-20 11 years ago
files MRG: merge ChangeLog for nagios fix 11 years ago
man DOC: set realistic expectations of what fail2ban protects against 11 years ago
.coveragerc TST+BF: Use separate coveragerc for Travis CI 12 years ago
.gitignore MRG: from master again 2014-01-01 11 years ago
.project
.pydevproject
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch obvious problems 13 years ago
.travis.yml MRG: from master to 0.9 2014-02-20 11 years ago
.travis_coveragerc TST: TravisCI coverage now includes untested systemd backend elements 12 years ago
COPYING
ChangeLog Merge branch 'master' into 0.9 11 years ago
DEVELOP MRG: from master again 2014-01-01 11 years ago
FILTERS DOC: filter documentation was bigger than DEVELOP so separated it out. Hopefully it may get read more 11 years ago
MANIFEST MRG: merge from master 2014-01-19 11 years ago
README.Solaris DOC: fix ChangeLog merge 12 years ago
README.md DOC: set realistic expectations of what fail2ban protects against 11 years ago
THANKS MRG: from master to 0.9 2014-02-20 11 years ago
TODO added new date format support for ASSP SMTP Proxy 12 years ago
fail2ban-2to3 TST: Fix up fail2ban python3 scripts 12 years ago
fail2ban-testcases-all ENH+TST: Move fail2ban-* scripts to bin/ 12 years ago
fail2ban-testcases-all-python3 TST: Fix up fail2ban python3 scripts 12 years ago
kill-server
setup.cfg Merge branch 'master' into 0.9 12 years ago
setup.py TST+BF: Add tests for python actions, including test for smtp.py 11 years ago

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.9.0a2                2014/??/??

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 /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