Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileSize	287540
MD5	296E18A9B089BFEFAEF25489CB22FD25
PackageDescription	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, qmail, 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 -- default installation uses iptables for banning. 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
PackageMaintainer	Yaroslav Halchenko <debian@onerussian.com>
PackageName	fail2ban
PackageSection	net
PackageVersion	0.9.6-2
SHA-1	A0E32F96A89E86D4994CE9BF224DCA1E281334CC
SHA-256	E68BB7AFBD68C53741630C834AB78F093BFC393E88F40B37DC5904F773A371DD

Key	Value
FileSize	246710
MD5	C8A52420FE4F84624C9052D1C5A536F1
PackageDescription	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, qmail, 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 -- default installation uses iptables for banning. 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
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	fail2ban
PackageSection	net
PackageVersion	0.9.7-2
SHA-1	61E92ADB586368933330C293210B31431573E5D4
SHA-256	F9DFA8B1A28E43769C09D84C657F69E44F2687648676B3B0DFFB23B929620361

Key	Value
FileSize	244164
MD5	5C635C14D4404EF2EF4C943EDA15ED16
PackageDescription	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, qmail, 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 -- default installation uses iptables for banning. 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
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	fail2ban
PackageSection	net
PackageVersion	0.9.6-1
SHA-1	F64D159FE5506D5931EBC5F2BBC1D9D621CCE895
SHA-256	6F30F9E522BEE2D7724FBC32F7704FCB97252915B04AB796D69C3FE7E2AFE36D