Go to file
Yaroslav Halchenko 39bc2e34f1 Release 0.8.9
-----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.12 (GNU/Linux)
 
 iEYEABECAAYFAlGRBZ8ACgkQjRFFY3XAJMhqzwCgvUsrv6cSjo1d8YCQUA8Na0Kk
 44QAoKk7X2sqFM+wvj2vK3stsHa/80qm
 =iBfR
 -----END PGP SIGNATURE-----

Merge tag '0.8.9' into debian

Release 0.8.9

* tag '0.8.9':
  BF: add missing files to MANIFEST (I think we shoult not rely on sdist anyways -- 'git tag' tarballs are more thorough ;) )
2013-05-13 11:24:26 -04:00
client ENH: remove use of $Revision and $Date SVN tags 2013-05-08 13:59:09 -04:00
common All the (version) updates for the release of 0.8.9 2013-05-13 11:00:44 -04:00
config DOC: inline commends with ';' are in effect only if ';' follows as space 2013-05-12 21:42:59 -04:00
debian added new sample jails definitions for ssh-route, ssh-iptables-ipset{4,6}, roundcube-auth, sogo-auth, mysqld-auth 2013-05-13 11:18:23 -04:00
doc Fixed typos 2013-03-10 22:05:33 +00:00
files Merge pull request #217 from kwirk/bash-completion 2013-05-08 07:03:09 -07:00
man All the (version) updates for the release of 0.8.9 2013-05-13 11:00:44 -04:00
server ENH: now we know that logging handlers closing was still buggy in 2.6.2 2013-05-12 22:55:02 -04:00
testcases BF: (travis) relax the test for needed to be presented installed directories -- allow new 2013-05-12 23:42:57 -04:00
.coveragerc TST+BF: Use separate coveragerc for Travis CI 2013-03-29 20:14:13 +00:00
.gitignore ENH: git ignore failed patch reminants 2013-03-16 13:53:51 +11:00
.project
.pydevproject
.pylintrc ENH: added a .pylintrc to help with consistent appearance and catch obvious problems 2011-10-04 10:55:16 -04:00
.travis.yml TST: Coverage for coveralls.io should only be run on success 2013-04-14 15:56:14 +01:00
.travis_coveragerc TST: Add gamin support for Travis CI 2013-03-30 18:17:01 +00:00
COPYING - Added ISO 8601 date/time format. 2008-05-18 19:53:18 +00:00
ChangeLog All the (version) updates for the release of 0.8.9 2013-05-13 11:00:44 -04:00
DEVELOP DOC: macports distribution of fail2ban 2013-05-03 16:59:54 +10:00
MANIFEST BF: add missing files to MANIFEST (I think we shoult not rely on sdist anyways -- 'git tag' tarballs are more thorough ;) ) 2013-05-13 11:24:07 -04:00
README.Solaris DOC: inline commends with ';' are in effect only if ';' follows as space 2013-05-12 21:42:59 -04:00
README.md All the (version) updates for the release of 0.8.9 2013-05-13 11:00:44 -04:00
THANKS added new date format support for ASSP SMTP Proxy 2013-05-03 00:56:46 -04:00
TODO added new date format support for ASSP SMTP Proxy 2013-05-03 00:56:46 -04:00
fail2ban-client ENH: "is None" instead of "== None" + tune ups in headers 2013-05-02 23:25:43 -04:00
fail2ban-regex ENH: deleted trailing spaces in fail2ban- cmdline tools 2013-03-29 12:31:50 -04:00
fail2ban-server ENH: deleted trailing spaces in fail2ban- cmdline tools 2013-03-29 12:31:50 -04:00
fail2ban-testcases ENH: issue a warning if jail name is longer than 19 symbols (Close #222) 2013-05-12 22:19:50 -04:00
fail2ban-testcases-all ENH: fail2ban-testcases-all -- pass cmdline options to fail2ban-testcases 2012-11-07 11:34:20 -05:00
kill-server
setup.cfg BF: Rename mentioning of README to README.md (Fixes #187) 2013-04-26 22:51:59 -04:00
setup.py BF: Rename mentioning of README to README.md (Fixes #187) 2013-04-26 22:51:59 -04:00

README.md

                     __      _ _ ___ _               
                    / _|__ _(_) |_  ) |__  __ _ _ _  
                   |  _/ _` | | |/ /| '_ \/ _` | ' \ 
                   |_| \__,_|_|_/___|_.__/\__,_|_||_|
                   v0.8.9                  2013/05/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.9.tar.bz2
cd fail2ban-0.8.9
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 need some new features, you found bugs?

visit Issues and if your issue is not yet known -- file a bug report.

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