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
Sergey G. Brester 246d0e1100
Merge pull request #3216 from jerrykan/fix_missing_assert
3 years ago
.github Update FUNDING.yml 3 years ago
bin
config implements new interpolation variable `%(fail2ban_confpath)s` (automatically substituted from config-reader path, default `/etc/fail2ban` or `/usr/local/etc/fail2ban` depending on distribution); `ignorecommands_dir` is unneeded anymore, thus removed from `paths-common.conf`; 3 years ago
doc
fail2ban Add missing assert in Fail2banRegexTest.testFrmtOutput 3 years ago
files Merge pull request #2182 from orlitzky/openrc-improvements 3 years ago
man Fix typo found by lintian (Debian static analyzer) 3 years ago
.coveragerc
.gitattributes Display ChangeLog as a Markdown document 3 years ago
.gitignore
.mailmap
.project
.pylintrc
.travis.yml drop support for python 2.6 (hardly possible in modern CIs, new features would expect OrderedDicts, etc) 3 years ago
CONTRIBUTING.md
COPYING
ChangeLog drop support for python 2.6 (hardly possible in modern CIs, new features would expect OrderedDicts, etc) 3 years ago
DEVELOP Update information reg. ipdns.py as successor for dnsutils.py 6 years ago
FILTERS Add blank line so markdown renders correctly 4 years ago
MANIFEST Merge remote-tracking branch 'remotes/sebres/1.0-breakdown-safe-actions' with master; 3 years ago
MANIFEST.in
README.Solaris
README.md drop support for python 2.6 (hardly possible in modern CIs, new features would expect OrderedDicts, etc) 3 years ago
RELEASE
THANKS
TODO
Vagrantfile
fail2ban-2to3
fail2ban-testcases-all
fail2ban-testcases-all-python3
kill-server
setup.cfg
setup.py Merge pull request #2182 from orlitzky/openrc-improvements 3 years ago

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v1.0.1.dev1            20??/??/??

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.

Since v0.10 fail2ban supports the matching of IPv6 addresses.

This README is a quick introduction to Fail2Ban. More documentation, FAQ, and HOWTOs to be found on fail2ban(1) manpage, Wiki, Developers documentation 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-1.0.1.tar.bz2
cd fail2ban-1.0.1
sudo python setup.py install

Alternatively, you can clone the source from GitHub to a directory of Your choice, and do the install from there. Pick the correct branch, for example, master or 0.11

git clone https://github.com/fail2ban/fail2ban.git
cd fail2ban
sudo 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. You can verify that you have the correct version installed with

fail2ban-client version

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:

  • travis-ci.org: tests status / tests status (0.11 branch) / tests status (0.10 branch)

  • coveralls.io: Coverage Status / Coverage Status (0.11 branch) / Coverage Status / (0.10 branch)

  • codecov.io: codecov.io / codecov.io (0.11 branch) / codecov.io (0.10 branch)

Contact:

Bugs, feature requests, discussions?

See CONTRIBUTING.md

You just appreciate this program:

Send kudos to the original author (Cyril Jaquier) 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