Parents (Total: 4)

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

Key	Value
FileSize	329392
MD5	40EF3A3CA5EE887846A88FE947E0C220
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/nftables -- default installation uses iptables for banning. nftables is also suported. 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.10.2-2
SHA-1	629EA6CFF5E20C2686B533BDB1F01D3D6A87BFF5
SHA-256	F2B301028038A12E3C7E20579D75D2A75CC01CE836A1771F364EBCEBB3869B13

Key	Value
FileSize	384644
MD5	D26A26ECA5632E58CDD39C97E1ABEB46
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/nftables -- default installation uses iptables for banning. nftables is also suported. 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.10.2-2.1
SHA-1	B36B6A7DACB7E258547368ED435CF1AF33C2984F
SHA-256	C7941FFBE271CA12A984F57B2B501B8A5E3BC8248808DB5E23DC6D3F223C114A

Key	Value
FileSize	329440
MD5	B292F1B053101C071324EA3BAE863580
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/nftables -- default installation uses iptables for banning. nftables is also suported. 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.10.2-2.1
SHA-1	FCFD7C6D200B5B1E6F6522E74780C4F9AE4FF92D
SHA-256	14F21CC23AA52369217D173EF0DA3BBAE61913D5B0791368C52A3B70C0981FEE

Key	Value
FileSize	385708
MD5	C6D10419667B95F6E1CD122178E5B6C4
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/nftables -- default installation uses iptables for banning. nftables is also suported. 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.10.2-2~bpo9+1
SHA-1	701288400DBE6748D37F52C4A11B2AC2BE616CD3
SHA-256	BF194A3C43450F3E1D01030F97425D04CC806ACFF744BC7BE08B52511C33725E