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.
 
 
 
Yaroslav Halchenko 1784205ff8 DOC: Slight tune up to RELEASE doc -- no need for PYTHONPATH to run tests 10 years ago
bin BF: fail2ban-regex does not read '.local' file of given filter (gh-954) 10 years ago
config Merge remote-tracking branch 'upstream/master' into bf/1000-asteriskBlocksSelf 10 years ago
doc DOC: sphinx documentation 11 years ago
fail2ban Initial changes for the release -- simplified ChangeLog header etc 10 years ago
files added $named and ufw to debian-initd (Debian bug #776572) 10 years ago
man Initial changes for the release -- simplified ChangeLog header etc 10 years ago
.coveragerc TST+BF: Use separate coveragerc for Travis CI 12 years ago
.gitignore Add .idea dir to .gitignore 10 years ago
.project
.pydevproject
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch obvious problems 13 years ago
.travis.yml BF: if install pypy -- come back to original directory 10 years ago
.travis_coveragerc TST: TravisCI coverage now includes untested systemd backend elements 12 years ago
CONTRIBUTING.md Added to CONTRIBUTING.md minimal guidelines for PRs 10 years ago
COPYING
ChangeLog Initial changes for the release -- simplified ChangeLog header etc 10 years ago
DEVELOP DOC: documentation about available vagrantfile setup 10 years ago
FILTERS DOC: sphinx documentation 11 years ago
MANIFEST MANIFEST: updated for some new files, sorted all entries, removed some duplicates 10 years ago
MANIFEST.in Add ignorecommands to MANIFEST*'s 10 years ago
README.Solaris DOC: minor changes just to trigger the build 11 years ago
README.md Initial changes for the release -- simplified ChangeLog header etc 10 years ago
RELEASE DOC: Slight tune up to RELEASE doc -- no need for PYTHONPATH to run tests 10 years ago
THANKS Merge branch 'master' of https://github.com/rumple010/fail2ban 10 years ago
TODO DOC: deadlock resolved with locking introduced in 3a58d0e and d07df66 now uses subprocess.Popen. 11 years ago
Vagrantfile Vagrant with two Ubuntu Trusty64 boxes 11 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 Add trailing comma back to list 10 years ago

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.9.2                  2015/04/26

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.2.tar.bz2
cd fail2ban-0.9.2
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