Key | Value |
---|---|
FileName | ./etc/fail2ban/action.d/osx-ipfw.conf |
FileSize | 2214 |
MD5 | 4E029C2591EBC57D10316968885B4E36 |
SHA-1 | 10DE5A601A5AEC5FDF97BF51FF614FEC9AAAD6CF |
SHA-256 | 10170CA25CCF1D3AB889B57E8797A198CDBA9C52FE884A88124A1628DB5BBA45 |
SSDEEP | 48:E6cq0ICe6UCbLykCtqm5PBX6PjPmKTGV+5oAT0A/CbW1at:0VHylw8+PmKi8GAp/C4Y |
TLSH | T109411F5B37AD33B9429A40A0854FB5909B3BE114F3221EB9726DC64277191BCC2AB987 |
hashlookup:parent-total | 14 |
hashlookup:trust | 100 |
The searched file hash is included in 14 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 | 214506 |
MD5 | 40B011BEDAF5FEDDE624F2A5FD1BA453 |
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. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | fail2ban |
PackageSection | net |
PackageVersion | 0.9.1-1 |
SHA-1 | F37AE165E2C8CE48360EC3514CD0C19D37E754DF |
SHA-256 | D5FA6B77F792B81A825ACF93286DACDD7C7C0A819F4AF3F297150BF6550FA813 |
Key | Value |
---|---|
MD5 | DC82835C26961A4A7C8E8EEFF81EC8A1 |
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.el5 |
PackageVersion | 0.8.14 |
SHA-1 | 3D791690019FE884B31EEA77F46E578DE9FB3D50 |
SHA-256 | 60A5AB5389CDE3DBB4CF973004AD7E7373B302E2C7F5AB4194C58C82157CB949 |
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 | 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 |
---|---|
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 |
---|---|
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 | 165378 |
MD5 | B0B9A415794D02ACAB6B19753A1ECD9E |
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. |
PackageMaintainer | Yaroslav Halchenko <debian@onerussian.com> |
PackageName | fail2ban |
PackageSection | net |
PackageVersion | 0.8.13-1 |
SHA-1 | D50AD0FED3D07143363D033A2EC0CBEDD477E7BB |
SHA-256 | 42537947E8FCFC0951B8511F26F35A92FA070994E73A46D2F7CE6842F6BE96EA |
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 | 134212 |
MD5 | 98F0E6B7D7D95C06BE7B1859C1187E01 |
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. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | fail2ban |
PackageSection | net |
PackageVersion | 0.8.13-1 |
SHA-1 | 93A769EF3205A5E7CB20E8B00DBA31332DCF77B3 |
SHA-256 | 7984DE1916041BEEDAB9D51B79ED218164FBE8D9465DE161045E2DFB196BF88A |
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 |
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 |