fail2ban 1.0.2-1 source package in Ubuntu

Changelog

fail2ban (1.0.2-1) unstable; urgency=medium

  * New upstream release

 -- Sylvestre Ledru <email address hidden>  Wed, 09 Nov 2022 17:42:47 +0100

Upload details

Uploaded by:
Debian Python Team
Uploaded to:
Sid
Original maintainer:
Debian Python Team
Architectures:
all
Section:
net
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Lunar release universe net

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
fail2ban_1.0.2-1.dsc 2.0 KiB fd22f66dd74a6799d60c28618d1865b295cd11010d83d14d62cb0c9f00c03c6c
fail2ban_1.0.2.orig.tar.gz 569.6 KiB ae8b0b41f27a7be12d40488789d6c258029b23a01168e3c0d347ee80b325ac23
fail2ban_1.0.2-1.debian.tar.xz 28.6 KiB e119fe181a0a98ef9f29d4a42c61843c2ee4b4e9acc9e7ba395a1e878a82b427

Available diffs

No changes file available.

Binary packages built by this source

fail2ban: ban hosts that cause multiple authentication errors

 Fail2ban monitors log files (e.g. /var/log/auth.log,
 /var/log/apache/access.log) and temporarily or persistently bans
 failure-prone addresses by updating existing firewall rules. Fail2ban
 allows easy specification of different actions to be taken such as to ban
 an IP using iptables or hostsdeny rules, or simply to send a notification
 email.
 .
 By default, it comes with filter expressions for various services
 (sshd, Apache, proftpd, sasl, etc.) but configuration can be
 easily extended for monitoring any other text file. All filters and
 actions are given in the config files, thus fail2ban can be adopted
 to be used with a variety of files and firewalls. Following recommends
 are listed:
 .
  - iptables/nftables -- default installation uses iptables for banning.
    nftables is also supported. You most probably need it
  - whois -- used by a number of *mail-whois* actions to send notification
    emails with whois information about attacker hosts. Unless you will use
    those you don't need whois
  - python3-pyinotify -- unless you monitor services logs via systemd, you
    need pyinotify for efficient monitoring for log files changes