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
sebres 2ed414ed09
fixed possible RCE vulnerability, unset escape variable (default tilde) stops consider "~" char after new-line as composing escape sequence
3 years ago
.github DOC: adjusted ISSUE_TEMPLATE.md picking on @sebres's version 9 years ago
bin RF: Replace old fashioned "except E , e" with "except E as e" (Closes #1537) 8 years ago
config fixed possible RCE vulnerability, unset escape variable (default tilde) stops consider "~" char after new-line as composing escape sequence 3 years ago
doc DOC: sphinx documentation 11 years ago
fail2ban (grave) closes gh-2431: replace newlines in message from systemd journal (otherwise multi-line parsing is broken, because removal of matched string from multi-line buffer window is confused by extra new-lines, so they are retained and got matched on every followed message). 6 years ago
files gentoo-initd: add descriptions 7 years ago
man Preparing for 0.9.7 release 8 years ago
.coveragerc Consolidate coveragerc configs into .coveragerc (delete .travis_coveragerc) 10 years ago
.gitignore Add .idea dir to .gitignore 10 years ago
.mailmap ENH: .mailmap file to bring some names together for git shortlog -sn 9 years ago
.project
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch obvious problems 13 years ago
.travis.yml try to fix travis build for pypy3 (after switch to 'pypy3.3-5.2-alpha1' the test cases seems to never run anymore). 8 years ago
CONTRIBUTING.md Added to CONTRIBUTING.md minimal guidelines for PRs 10 years ago
COPYING - Added ISO 8601 date/time format. 17 years ago
ChangeLog nginx-http-auth: match usernames with spaces 7 years ago
DEVELOP DOC: Use coverage report and optionally coverage html 10 years ago
FILTERS Update FILTERS 8 years ago
MANIFEST Added newly added files to MANIFEST 8 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 minor fix with reindent 7 years ago
RELEASE life is going on 8 years ago
THANKS filter.d/dovecot.conf update: 8 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 BF: prefer sys.argv[0] by retrieving of root resp. bin path: __file__ seems to be overwritten sometimes on some python versions (e.g. bug of 2.6 by running under cProfile, etc.) 8 years ago

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.9.7.dev0             2017/??/??

Fail2Ban: ban hosts that cause multiple authentication errors

Fail2Ban scans log files like /var/log/auth.log and bans IP addresses conducting too many failed login attempts. It does this by updating system firewall rules to reject new connections from those IP addresses, for a configurable amount of time. Fail2Ban comes out-of-the-box ready to read many standard log files, such as those for sshd and Apache, and is easily configured to read any log file of your choosing, for any error you wish.

Though Fail2Ban is able to reduce the rate of incorrect authentication attempts, it cannot eliminate the risk presented by weak authentication. Set up 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, and HOWTOs to be found on fail2ban(1) manpage and the website: https://www.fail2ban.org

Installation:

It is possible that Fail2Ban is already packaged for your distribution. In this case, you should use that instead.

Required:

Optional:

To install:

tar xvfj fail2ban-0.9.7.tar.bz2
cd fail2ban-0.9.7
python setup.py install

This will install Fail2Ban into the python library directory. The executable scripts are placed into /usr/bin, and configuration in /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.

Please note that the system init/service script is not automatically installed. To enable fail2ban as an automatic service, simply copy the script for your distro from the files directory to /etc/init.d. Example (on a Debian-based system):

cp files/debian-initd /etc/init.d/fail2ban
update-rc.d fail2ban defaults
service fail2ban start

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

  • codecov.io

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