Parents (Total: 10)

The searched file hash is included in 10 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
CRC32	A384B5E1
FileName	19979
FileSize	227028
MD5	D4EEDCCF04345C9F642391F7ADCECB86
OpSystemCode	362
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.3-1
ProductCode	184814
RDS:package_id	184814
SHA-1	5036D57B893C077059EDAA930B763BBC5F180F05
SHA-256	77956AE0E2809BBBB6E76F7E228A3B453A4A8DD9F005E812BACD708714DDDB8C
SpecialCode
db	nsrl_legacy
insert-timestamp	1648751507.4833016
source	RDS_2022.03.1_legacy.db

Key	Value
MD5	ADC85DB498A8817F65B419BD83F11723
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	Fedora Project
PackageName	fail2ban-server
PackageRelease	3.fc24
PackageVersion	0.9.3
SHA-1	8000E8B588818EDBF21A1BE8E105FE88D14AB22F
SHA-256	D7AAFEE94F0EBE9799455EB49EEAD76C882DFC4ED53598C28B65053C678997B9

Key	Value
MD5	84644A1819D9AD33C6EC6560B19488AD
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	Fedora Project
PackageName	fail2ban-server
PackageRelease	3.fc24
PackageVersion	0.9.3
SHA-1	A056C8900481FB74671B76C6AFBE7B1C4F3D830B
SHA-256	CA5E36FFB1ED06B3AE385D7B7B78249F8AACE0249BEE32EF199B7DE8C95022EE

Key	Value
MD5	7DEB4D97509EF595A3B2AE8B2DADD33E
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	Fedora Project
PackageName	fail2ban-server
PackageRelease	1.el7
PackageVersion	0.9.7
SHA-1	7AEDC73283CB2965D4AD88919143553E38A69FE9
SHA-256	FF460F1595C970B55F4249CC0CA22BE14604B968EAA1E5D790F364FD9B820674

Key	Value
MD5	23598ACABD0BF151FE8AA55FE98406DA
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	1.el7
PackageVersion	0.9.7
SHA-1	10BEF8241FF556BB03B6EEA32B91988824871A82
SHA-256	5ED3325C027F979D43E761D5DBE26A4FB001E4AB2C542560553F22DE5BBD0E25

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	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