78e1a13fad
* '_tent/cache-config-read' of https://github.com/sebres/fail2ban: code review, change log entries added; reset share/cache storage (if we use 'reload' in client with interactive mode) normalize tabs/spaces in docstrings; cache-config-read-v2 merged; logging normalized, set log level for loading (read or use shared) file(s) to INFO; prevent to read some files twice by read inside "_getIncludes" and by "read" self (occurred by only one file); code review; more stable config sharing, configurator always shares it config readers now; code review: use the same code (corresponding test cases - with sharing on and without it); rewritten caching resp. sharing of ConfigReader and SafeConfigParserWithIncludes (v.2, first and second level cache, without fingerprinting etc.); code review ConfigReader/ConfigWrapper renamed as suggested from @yarikoptic; + code clarifying (suggested also); Partially merge remote-tracking from 'sebres:cache-config-read-820': test cases extended, configurator.py adapted for test case. ENH: keep spitting out logging to the screen in LogCaptureTestCases if HEAVYDEBUG test case for check the read of config files will be cached; more precise by test ConfigWrapper class introduced: sharing of the same ConfigReader object between JailsReader and JailReader (don't read jail config each jail); sharing of the same DefinitionInitConfigReader (ActionReader, FilterReader) between all jails using that; cache of read a config files was optimized; test case extended for all types of config readers; config cache optimized - prevent to read the same config file inside different resources multiple times; test case: read jail file only once; test case for check the read of config files will be cached; caching of read config files, to make start of fail2ban faster, see issue #820 |
||
---|---|---|
bin | ||
config | ||
doc | ||
fail2ban | ||
files | ||
man | ||
.coveragerc | ||
.gitignore | ||
.project | ||
.pydevproject | ||
.pylintrc | ||
.travis.yml | ||
.travis_coveragerc | ||
CONTRIBUTING.md | ||
COPYING | ||
ChangeLog | ||
DEVELOP | ||
FILTERS | ||
MANIFEST | ||
MANIFEST.in | ||
README.Solaris | ||
README.md | ||
RELEASE | ||
THANKS | ||
TODO | ||
Vagrantfile | ||
fail2ban-2to3 | ||
fail2ban-testcases-all | ||
fail2ban-testcases-all-python3 | ||
kill-server | ||
setup.cfg | ||
setup.py |
README.md
__ _ _ ___ _
/ _|__ _(_) |_ ) |__ __ _ _ _
| _/ _` | | |/ /| '_ \/ _` | ' \
|_| \__,_|_|_/___|_.__/\__,_|_||_|
v0.9.0 2014/03/14
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:
- pyinotify >= 0.8.3
- Linux >= 2.6.13
- gamin >= 0.0.21
- systemd >= 204
To install, just do:
tar xvfj fail2ban-0.9.0.tar.bz2
cd fail2ban-0.9.0
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:
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