mirror of https://github.com/fail2ban/fail2ban
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.
Cyril Jaquier
3252b15890
|
18 years ago | |
---|---|---|
config | 18 years ago | |
confreader | 19 years ago | |
firewall | 19 years ago | |
log-test | 19 years ago | |
logreader | 18 years ago | |
man | 19 years ago | |
utils | 18 years ago | |
.project | 18 years ago | |
.pydevproject | 18 years ago | |
CHANGELOG | 18 years ago | |
MANIFEST | 19 years ago | |
README | 18 years ago | |
TODO | 19 years ago | |
fail2ban | 18 years ago | |
fail2ban.py | 18 years ago | |
setup.cfg | 20 years ago | |
setup.py | 19 years ago | |
version.py | 18 years ago |
README
__ _ _ ___ _ / _|__ _(_) |_ ) |__ __ _ _ _ | _/ _` | | |/ /| '_ \/ _` | ' \ |_| \__,_|_|_/___|_.__/\__,_|_||_| ============================================================= Fail2Ban (version 0.6.2) 2006/12/11 ============================================================= 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 is my first Python program. Moreover, English is not my mother tongue... More details: ------------- Fail2Ban is rather simple. I have a home server connected to the Internet which runs apache, samba, sshd, ... I see in my logs that people are trying to log into my box using "manual" brute force or scripts. They try 10, 20 and sometimes more user/password (without success anyway). In order to discourage these script kiddies, I wanted that sshd refuse login from a specific ip after 3 password failures. After some Google searches, I found that sshd was not able of that. So I search for a script or program that do it. I found nothing :-( So I decide to write mine and to learn Python :-) For each sections defined in the configuration file, Fail2Ban tries to find lines which match the failregex. Then it retrieves the message time using timeregex and timepattern. It finally gets the ip and if it has already done 3 or more password failures in the last banTime, the ip is banned for banTime using a firewall rule. This rule is set by the user in the configuration file. Thus, Fail2Ban can be adapted for lots of firewall. After banTime, the rule is deleted. Notice that if no "plain" ip is available, Fail2Ban try to do DNS lookup in order to found one or several ip's to ban. Sections can be freely added so it is possible to monitor several daemons at the same time. Runs on my server and does its job rather well :-) The idea is to make fail2ban usable with daemons and services that require a login (sshd, telnetd, ...) and with different firewalls. Installation: ------------- Require: python-2.4 (http://www.python.org) To install, just do: > tar xvfj fail2ban-0.6.2.tar.bz2 > cd fail2ban-0.6.2 > python setup.py install This will install Fail2Ban into /usr/lib/fail2ban. The fail2ban executable is placed into /usr/bin. Gentoo: ebuilds are available on the website. Debian: Fail2Ban is in Debian unstable. RedHat: packages are available on the website. Fail2Ban should now be correctly installed. Just type: > fail2ban -h to see if everything is alright. You can configure fail2ban with a config file. Different kind of configuration files are available: iptables: copy config/fail2ban.conf.iptables to /etc/fail2ban.conf hosts.deny: copy config/fail2ban.conf.hostsdeny to /etc/fail2ban.conf shorewall: copy config/fail2ban.conf.shorewall to /etc/fail2ban.conf Do not forget to edit fail2ban.conf to meet your needs. You can use the initd script available in config/. Copy <dist>-initd to /etc/init.d/fail2ban. Gentoo users must copy gentoo-confd to /etc/conf.d/fail2ban. You can start fail2ban: > /etc/init.d/fail2ban start Gentoo users can add it to the default runlevel: > rc-update add fail2ban default Configuration: -------------- You can configure fail2ban using the file /etc/fail2ban.conf or using command line options. Command line options override the value stored in fail2ban.conf. Here are the command line options: -b start in background -c <FILE> read configuration file FILE -p <FILE> create PID lock in FILE -h display this help message -i <IP(s)> IP(s) to ignore -k kill a currently running instance -r <VALUE> allow a max of VALUE password failure [maxfailures] -t <TIME> ban IP for TIME seconds [bantime] -f <TIME> lifetime in seconds of failed entry [findtime] -v verbose. Use twice for greater effect -V print software version Please note that a vulnerability (CVE-2006-6302) affects version < 0.6.2. Since 0.6.2, a named group "host" was added to "failregex". This group must match the host address. Old configuration files will still work but will generate a warning. In this case, please update your configuration file. Contact: -------- You need some new features, you found bugs or you just appreciate this program, you can contact me at : Website: http://fail2ban.sourceforge.net Cyril Jaquier: <lostcontrol@users.sourceforge.net> Thanks: ------- Kévin Drapel, Marvin Rouge, Sireyessire, Robert Edeker, Tom Pike, Iain Lea, Andrey G. Grozin, Yaroslav Halchenko, Jonathan Kamens, Stephen Gildea, Markus Hoffmann, Mark Edgington, Patrick Börjesson, kojiro, zugeschmiert, René Berber 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA