fail2ban 1.1.0-2ubuntu2 source package in Ubuntu

Changelog

fail2ban (1.1.0-2ubuntu2) oracular; urgency=medium

   [ Åka Sikrom (akrosikam) ]
   * Add python3-setuptools runtime dependency needed for Python3.12
     to use distutils.version (LP: #2055114)

 -- Gianfranco Costamagna <email address hidden>  Tue, 21 May 2024 09:43:51 +0200

Upload details

Uploaded by:
Gianfranco Costamagna
Uploaded to:
Oracular
Original maintainer:
Debian Python Team
Architectures:
all
Section:
net
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Oracular: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
fail2ban_1.1.0.orig.tar.gz 589.7 KiB 474fcc25afdaf929c74329d1e4d24420caabeea1ef2e041a267ce19269570bae
fail2ban_1.1.0-2ubuntu2.debian.tar.xz 29.4 KiB b6b18a03f289ccb4472ac39c93cbc8bdc2f51c644531e2d1b42a9a3148789735
fail2ban_1.1.0-2ubuntu2.dsc 2.0 KiB df13640d0fa426b9833e5b89e77403fbe74e498c33d4b454ddfc611be997d440

View changes file

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