Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 6784 |
MD5 | 7AEDA4FD3A9B37B0D0E163FAB209A01E |
SHA-1 | 75CDC5927F3C87C9BDF722051445DA3CF8DB40AE |
SHA-256 | AFA80DCF1D126B9771DE334388FEF9FA9947261AB0FD3FE172B04E540DD9CAFF |
SSDEEP | 96:gxtZyayBB+BbRBphwpdYGc3oBnGijEkIlxCqcy9ZrU+g:4ZyayBw5RzhwpG8B54xlgC |
TLSH | T177E1DA8BFB93CC37C8905939D67B07116370ECC587839B03899016812D7A5D85ED6596 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 5F5015274F03163C49A89785D6B9C321 |
PackageArch | armv7hl |
PackageDescription | IP sets are a framework inside the Linux kernel since version 2.4.x, which can be administered by the ipset utility. Depending on the type, currently an IP set may store IP addresses, (TCP/UDP) port numbers or IP addresses with MAC addresses in a way, which ensures lightning speed when matching an entry against a set. If you want to: - store multiple IP addresses or port numbers and match against the collection by iptables at one swoop; - dynamically update iptables rules against IP addresses or ports without performance penalty; - express complex IP address and ports based rulesets with one single iptables rule and benefit from the speed of IP sets then ipset may be the proper tool for you. |
PackageMaintainer | Fedora Project |
PackageName | ipset |
PackageRelease | 1.fc32 |
PackageVersion | 7.6 |
SHA-1 | 15D96D94C0CC984E247AF242B6D4BB8D72183806 |
SHA-256 | 79BFA081AFE78F70624C779639D9F7ACFF93B0E642DDDDD14350FC81535EDE38 |