Parents (Total: 5)

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

Key	Value
MD5	8C7381A82C5F83F2C3A7F1A2A115B16E
PackageArch	noarch
PackageDescription	Fail2ban scans log files like /var/log/pwdfail or /var/log/apache/error_log and bans IP that makes too many password failures. It updates firewall rules to reject the IP address. To use the hostsdeny and shorewall actions you must install tcp_wrappers and shorewall respectively.
PackageMaintainer	Fedora Project
PackageName	fail2ban
PackageRelease	1.el6.1
PackageVersion	0.9.6
SHA-1	82976B33BE986F928F3B895B3CE9CEEA59773356
SHA-256	5494D678669606897C1CFB851921A8833797F6F697822AA68A1ACA03FA7D942B

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

Key	Value
MD5	42B1CE9BFAF435DC41F10491AF42F249
PackageArch	noarch
PackageDescription	This package contains the core server components for Fail2Ban with minimal dependencies. You can install this directly if you want to have a small installation and know what you are doing.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	fail2ban-server
PackageRelease	3.el7
PackageVersion	0.9.5
SHA-1	0E41B59481336E90526E2648C69483457532D463
SHA-256	BC1FAB396B540610A903ED11092336280BDA58AB7CEE060678226406CAE162AC

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	238368
MD5	39F32E97DC0FF2CB1C1D5D734998CA37
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.5-1
SHA-1	3A45D72F6B98A1F431D4E47B45E02E4E44A3738D
SHA-256	15957088AFF14983E3BA5A24880DC0E3D22F1A76690CCAE6EFC717B6872C22B3