fail2ban (security/fail2ban) Updated: 2 weeks, 2 days ago Add to my watchlist
Fail2ban protects computer against brute-force attacksFail2ban scans log files (e.g. /var/log/apache/error_log) and bans IPs that show the malicious signs -- too many password failures, seeking for exploits, etc. Generally Fail2Ban then used to update firewall rules to reject the IP addresses for a specified amount of time, although any arbitrary other action (e.g. sending an email, or ejecting CD-ROM tray) could also be configured. Out of the box Fail2Ban comes with filters for various services (apache, curier, ssh, etc).
Version: 1.1.1 License: GPL-2+
GitHub
| Maintainers | ArtKoKo |
| Categories | security python |
| Homepage | https://www.fail2ban.org/ |
| Platforms | {darwin any} |
| Variants | - |
"fail2ban" depends on
lib (1)
build (2)
Ports that depend on "fail2ban"
No ports
Port notes
Do not edit the *.conf files in ${prefix}/etc/fail2ban: they are replaced on each upgrade. Put your settings in *.local files instead (e.g. ${prefix}/etc/fail2ban/jail.local), as explained in jail.conf. On an upgrade from 0.9.4, the old copies of the *.conf files are renamed *.conf.mp_<timestamp>.
The default ban action is pf. Bans are added to sub-anchors of the f2b anchor, which must be referenced in /etc/pf.conf:
anchor "f2b/*"
Start/stop fail2ban with: sudo port [un]load fail2ban A startup item has been generated that will aid in starting fail2ban with launchd. It is disabled by default. Execute the following command to start it, and to cause it to launch at startup:
sudo port load fail2ban
Port Health:
Loading Port Health