mirror of
https://github.com/fail2ban/fail2ban.git
synced 2026-03-11 08:55:31 +00:00
f5a8a8ac7c
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlGRBZ8ACgkQjRFFY3XAJMhqzwCgvUsrv6cSjo1d8YCQUA8Na0Kk 44QAoKk7X2sqFM+wvj2vK3stsHa/80qm =iBfR -----END PGP SIGNATURE----- Merge tag '0.8.9' into 0.9 (quite a bit of conflicts "resolved") 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 ;) ) All the (version) updates for the release of 0.8.9 BF: (travis) relax the test for needed to be presented installed directories -- allow new BF: (travis) if tests ran under coverage -- there is a traceback parts to report (thus > would be present) ENH: also print the failing traceback line in case of failure ENH: include explicit list of new files which should not be there upon "install --root" ENH: now we know that logging handlers closing was still buggy in 2.6.2 ENH: issue a warning if jail name is longer than 19 symbols (Close #222) DOC: inline commends with ';' are in effect only if ';' follows as space BF: Fix for filterpoll incorrectly checking for jailless state ENH: strengthen detection of working pyinotify ENH: use the same python executable for setup.py test ENH: actually tune up TraceBack to determine "unittest" portions of the stack across all python releases TST: Some primarily smoke tests for tests utils TST: cover few more lines in fail2banreader.py ENH: basic test for setup.py itself (when applicable, should greatly improve coverage ;) ) ENH: consistent operation of formatExceptionInfo + unittest for it ENH: point to the status of master branch on travis Conflicts: ChangeLog MANIFEST README.md fail2ban/version.py -- all of the above obvious version changes below files primarily needed just a bit of help in resolution config/jail.conf fail2ban/server/filterpoll.py fail2ban/server/server.py fail2ban/tests/servertestcase.py and following were more difficult -- git wasn't able to track renames/moves of the code fail2ban-testcases -- needed to introduce those changes to tests/utils.py testcases/clientreadertestcase.py -- manually applied patch from master testcases/utils.py -- manually applied patch from master
100 lines
3.7 KiB
Markdown
100 lines
3.7 KiB
Markdown
__ _ _ ___ _
|
|
/ _|__ _(_) |_ ) |__ __ _ _ _
|
|
| _/ _` | | |/ /| '_ \/ _` | ' \
|
|
|_| \__,_|_|_/___|_.__/\__,_|_||_|
|
|
v0.9.0a0 2013/05/??
|
|
|
|
## 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:
|
|
- [Python >= 2.4, including 3.x](http://www.python.org)
|
|
|
|
Optional:
|
|
- [pyinotify >= 0.8.3](https://github.com/seb-m/pyinotify)
|
|
- Linux >= 2.6.13
|
|
- [gamin >= 0.0.21](http://www.gnome.org/~veillard/gamin)
|
|
|
|
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:
|
|
------------
|
|
|
|
* [](https://travis-ci.org/fail2ban/fail2ban) travis-ci.org (master branch)
|
|
|
|
* [](https://coveralls.io/r/fail2ban/fail2ban)
|
|
|
|
Contact:
|
|
--------
|
|
|
|
### You need some new features, you found bugs?
|
|
visit [Issues](https://github.com/fail2ban/fail2ban/issues)
|
|
and if your issue is not yet known -- file a bug report.
|
|
|
|
### You would like to troubleshoot or discuss?
|
|
join the [mailing list](https://lists.sourceforge.net/lists/listinfo/fail2ban-users)
|
|
|
|
### 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](https://lists.sourceforge.net/lists/listinfo/fail2ban-users)
|
|
since Fail2Ban is "community-driven" for years now.
|
|
|
|
Thanks:
|
|
-------
|
|
|
|
See [THANKS](https://github.com/fail2ban/fail2ban/blob/master/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
|