Official source tarballs
We only provide source tarballs. Fail2ban is written in Python, thus no compilation is required. You can even run Fail2ban without installing it.
|wanna-be-released -- 0.8.x fixes||:||GIT 0.8 branch|
|wanna-be-released -- 0.9.x fixes||:||GIT master branch|
Source version control
In September 2011 development version control switched from SVN on SF to git, hosted on github. To contribute, please create your own fork of Fail2ban on github, push your changes into it and submit pull requests.
You will also be able to download complete source tarballs for any existing tag/release or development master from fail2ban Releases on github.
Fail2ban is also already packaged for most distributions by contributors. Many thanks to all of them and you might be better off relying on your distribution delivery and support channels:
|Gentoo||Packages are in Portage.|
|Debian||Packages are available here. Backport builds are available from NeuroDebian|
|Ubuntu||Packages are available here. Backport builds are available from NeuroDebian|
|Fedora||RPMs are available by simply running: yum install fail2ban|
|Red Hat/CentOS||RPMs are available through EPEL.|
|Gral Linux||RPMs are available here. These RPMs can be used on Centos 3 and RHAS 3 too.|
|Ipcop||Addon is available here. Thanks to Markus Hoffmann|
|Mandriva||RPMs are available through official contrib repository. Please run "urpmi fail2ban". Thanks to Tomasz Paweł Gajc|
|SUSE/openSUSE||RPMs are available here. Thanks to Andrej Semen|
|ArchLinux||Package is available in AUR.|
|Slackware||Packages are available here. Thanks to Cristian Vedovato. A SlackBuild script to generate Slackware packages is available here.|
|FreeBSD||Port is here.|
|Mac OS X||Available from MacPorts|