Parents (Total: 8)

The searched file hash is included in 8 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
MD5	C63BBF6119AA09145D83E865CA4EE0F9
PackageArch	noarch
PackageDescription	Fail2ban scans log files like /var/log/messages and bans IP addresses that makes too many password failures. It updates firewall rules to reject the IP address, can send e-mails, or set host.deny entries. These rules can be defined by the user. Fail2Ban can read multiple log files such as sshd or Apache web server ones.
PackageMaintainer	https://bugs.opensuse.org
PackageName	fail2ban
PackageRelease	lp151.1.1
PackageVersion	0.10.4
SHA-1	22C8D2DF4281F69862D943291BB587A6CB25893D
SHA-256	6BF6CD98B89F11DDA2F90FCFAC6604648636B41F160C2C242378EF3FD222FBA5

Key	Value
MD5	F856FBD595D5119D0B2740E26137B36C
PackageArch	noarch
PackageDescription	Fail2ban scans log files like /var/log/messages and bans IP addresses that makes too many password failures. It updates firewall rules to reject the IP address, can send e-mails, or set host.deny entries. These rules can be defined by the user. Fail2Ban can read multiple log files such as sshd or Apache web server ones.
PackageMaintainer	https://bugs.opensuse.org
PackageName	fail2ban
PackageRelease	lp150.1.1
PackageVersion	0.10.3.1
SHA-1	942641CE92A5F26108E70AA5AF156FFF14D0969B
SHA-256	403B5419E37C3BA9157DABB796AEA25D542EFDB97E52DE459F67113D09A89695

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
MD5	774F7DDAF109839D79EACE89D64FB949
PackageArch	noarch
PackageDescription	Fail2Ban scans log files like /var/log/secure and bans IP-addresses that have too many password failures within a specified time frame. It updates firewall rules to reject these IP addresses. The rules needed for this can be defined by the user. Fail2Ban can read multiple log files including sshd and Apache web server logs.
PackageMaintainer	kekepower <kekepower>
PackageName	fail2ban
PackageRelease	2.mga7
PackageVersion	0.10.4
SHA-1	79EA9B329C64BCC28BF78FACFFEFECDA70D4A977
SHA-256	C31293D8FB8A38262149A7B94D8F8E71A1F0699748C75D36308A53D7121032D6

Key	Value
MD5	C3F9D0417942EC6CF3938FFC895A8502
PackageArch	noarch
PackageDescription	Fail2ban scans log files like /var/log/messages and bans IP addresses that makes too many password failures. It updates firewall rules to reject the IP address, can send e-mails, or set host.deny entries. These rules can be defined by the user. Fail2Ban can read multiple log files such as sshd or Apache web server ones.
PackageMaintainer	https://bugs.opensuse.org
PackageName	fail2ban
PackageRelease	lp152.2.3
PackageVersion	0.10.4
SHA-1	4EA09D47C62DD200E532FD9AD6E3A72E59715D14
SHA-256	9C983F6776B735C8A1CE6D34A7751E67BA35C49AE8EB06599F8432CA905BD339

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