installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%

brew install fail2ban

provider-native install command

aperçu

Résumé du paquet

Scan log files and ban IPs showing malicious signs

Liens du projet

Commandes et alias

fail2ban-client
fail2ban-python
fail2ban-regex
fail2ban-server
fail2ban-testcases

historique

Historique du projet et usages

Fail2Ban is a long-running Python daemon and command-line toolkit for reacting to hostile log patterns by banning hosts through firewall actions. Its core appeal has stayed stable since the early releases: watch authentication and service logs, count repeated failures, and temporarily block the offending address.

Historique du projet

The official changelog records Fail2Ban releases back to 0.1.0 in October 2004. Early 0.x releases moved quickly through alpha, beta, and stable lines, with 0.6.0 stable in 2005, the 0.7 branch in 2006, and 0.8.0 stable in 2007. The README still credits Cyril Jaquier as original author and describes the project as community-driven for years.

The 0.9 series, beginning in 2014, marked the modern service-management era by adding a systemd journal backend. The 0.10 line followed with IPv6 work, including an alpha labeled for IPv6 support in 2016 and a 0.10.0 release in 2017. Later releases continued to refine journald, iptables, nftables, firewalld, pf, and service-specific filters.

The 1.x line arrived with 1.0.1 and 1.0.2 releases in 2022 and 1.1.0 in 2024. These releases focused less on changing the basic model and more on compatibility, security, and operational maintenance: Python version support, CVE fixes, systemd backend stability, IPv6 auto-detection, newer service log formats, and additional filters and actions.

Historique d'adoption

Fail2Ban became part of the standard Linux server-security toolbox because it matched the common shape of internet-facing Unix services: SSH, mail, web, and database daemons emitting failed-authentication logs. The project README says it is likely already packaged for a user's Linux distribution, and the supplied package-manager facts show broad availability across Alpine, Debian, Fedora/DNF, Homebrew, MacPorts, Nix, Arch, Ubuntu, and openSUSE.

Its adoption has been helped by configuration conventions that distributions can ship and administrators can override. Stock jails, filters, actions, and path files let package maintainers encode distribution-specific log locations while users keep local policy in `/etc/fail2ban`, especially `jail.local` and `jail.d` snippets.

Modes d'utilisation

A typical Fail2Ban deployment installs the daemon, enables selected jails such as `sshd`, and lets `fail2ban-server` monitor logs while administrators use `fail2ban-client` for status, reloads, and manual control. The README explicitly warns users to interact through `fail2ban-client` rather than calling the server directly.

The package also matters to operators because `fail2ban-regex` gives a local way to test filters against log samples before enabling bans. That workflow, plus filter and action directories, made Fail2Ban not just a daemon but a small domain-specific toolkit for converting service logs into firewall state.

Pourquoi les passionnés de paquets s'y intéressent

Fail2Ban is significant in package-manager culture because it is both ordinary and sharp-edged: a tiny install command can place a privileged daemon, distro-specific defaults, init/systemd integration, and firewall actions on a host. Packagers must get paths, service units, Python dependencies, and default actions right or administrators either get no protection or accidental lockouts.

It is also a classic example of a package whose value comes from accumulated operational knowledge. The code is important, but the long tail of maintained filters for OpenSSH, Apache, nginx, Postfix, Dovecot, Exim, and many other services is why administrators keep installing it.

Chronologie

2004: Fail2Ban 0.1.0 alpha released.
2005: 0.6.0 stable release published.
2007: 0.8.0 stable release published.
2014: 0.9.0 beta added systemd journal backend.
2016: 0.10.0 alpha introduced IPv6-support work.
2017: 0.10.0 released.
2020: 0.11.2 released.
2022: 1.0.1 and 1.0.2 released with compatibility and security fixes.
2024: 1.1.0 released with newer Python support and further backend/filter updates.

Related projects

OpenSSH, iptables, nftables, firewalld, pf, systemd-journald, DenyHosts, sshguard

Sources

posture de sécurité

Niveau de risque : orange

broad file, network, media, or database tool signal. formula declares a Homebrew service.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

broad file, network, media, or database tool signal
formula declares a Homebrew service

Signaux

metadata:service
text:client,server

Comportement d'installation

Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: /etc/fail2ban/jail.conf/etc/fail2ban/jail.local/etc/fail2ban/jail.d/*.conf/etc/fail2ban/filter.d/*.conf/etc/fail2ban/action.d/*.conf

exécutables

Exécutables installés

Commande	Type	Exposition	Note
`fail2ban-client`	exécutable	exécutable indexé	Découvert depuis l'index local des exécutables.
`fail2ban-python`	exécutable	exécutable indexé	Découvert depuis l'index local des exécutables.
`fail2ban-regex`	exécutable	exécutable indexé	Découvert depuis l'index local des exécutables.
`fail2ban-server`	exécutable	exécutable indexé	Découvert depuis l'index local des exécutables.
`fail2ban-testcases`	exécutable	exécutable indexé	Découvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-03

version du gestionnaire1.1.0

gestionnaire mis à jour2026-08-02

données localesinconnu

amontnon disponible

dernière version détectéenon détecté

OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquet	brew:fail2ban
Version	1.1.0
Gestionnaire de paquets	Homebrew
Page d'accueil	https://www.fail2ban.org/
Dépôt	https://github.com/fail2ban/fail2ban
Dernière mise à jour	2026-08-02T16:35:31+09:00
Pulse	updated
Bouteille	non enregistré
Service	aucun déclaré

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/fail2ban.yml

Sources utilisées

Geiger risk classifier
Nucleus package database
curated configuration and credential file locations
curated package history
pkgdb category and tag curation

Installer fail2ban avec Homebrew