| Key | Value |
|---|---|
| FileName | ./usr/sbin/ipset |
| FileSize | 6408 |
| MD5 | 4BFCD4A963ED0ABD56E21C533D931719 |
| SHA-1 | 1FBB596A61BA5C716C476BB1698D68C9D5A65D9F |
| SHA-256 | AED8973850091C5A165774437D05371B0DCC062D89F177C5C928DC438DD13034 |
| SSDEEP | 96:9fixU5sufBB+Bye+dMrNiy/dtT/ZVxvcpjCS:p5fBwAe+dMrNiy/jT/9cp |
| TLSH | T159D1C782F7A38BABC9E61B3CC5F707A973B3C401A3939B53C2842470AC971B45E16596 |
| 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 | 4679E4F59F43B60F1C2AD0EB03D4DE2F |
| PackageArch | armv7hl |
| PackageDescription | IP sets are a framework inside the Linux kernel since 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. ipset may be the proper tool for you, if you want to o store multiple IP addresses or port numbers and match against the collection by iptables at one swoop; o dynamically update iptables rules against IP addresses or ports without performance penalty; o express complex IP address and ports based rulesets with one single iptables rule and benefit from the speed of IP sets |
| PackageMaintainer | wally <wally> |
| PackageName | ipset |
| PackageRelease | 1.mga7 |
| PackageVersion | 7.1 |
| SHA-1 | 0D5530EAE7CF10F2C6767E4D54FCB74A60088FA8 |
| SHA-256 | 581D883E272F25DA838C6676BE886058A67A212A8B38DD8D0822CABADBFD1470 |