Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 6412 |
MD5 | 0EF2E640E0361E06E9F74F5EC2062A41 |
SHA-1 | 0E7588B348CF78E31FBA1C533541FE1E9D8F082E |
SHA-256 | BB1ECB2559093EAE71B24BED7D27761AEC98338FEAA44BB33B340492E4E429E6 |
SSDEEP | 96:5fix35sufBB+Bye+dMrNiyHftl1DjHkBtXcvVEvTpjCl0:lIfBwAe+dMrNiy1zfEBtXcoTpE |
TLSH | T1AAD18442F3E38F67C9D65A38C6F7075873B3C40167E3AB0386502575AC661B84E169D6 |
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 | 687B136FC7112FA9D844F084E5DBA3DC |
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 | luigiwalser <luigiwalser> |
PackageName | ipset |
PackageRelease | 1.mga7 |
PackageVersion | 7.10 |
SHA-1 | 629FE3DA6FB4AC5D2607349E1F0B0FA115145BA0 |
SHA-256 | 97C72A3C4BB9533F1F740EEAB70163FC5FACA5205988A3D7131BDFD5C70F9726 |