Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_netnet.so |
FileSize | 17712 |
MD5 | DAEA72AC17976D31CE632F96C37A399A |
SHA-1 | 2103FA39156E13CE7FE0B944584F5C0B8501FB75 |
SHA-256 | 4AB29F186228070BDD5658591D53C0569F0F4332F7BA9F259513807A4E7B7301 |
SSDEEP | 96:R64hBWBwY+UxIumeuZXPGxj5LXbXg8MJTiwSjb6k+iVvUBI5:Rr8+YdrB57T21667i |
TLSH | T10A825186E7A0CB3FC978473448EB0B35B6F6E06417B2035727286A392E577842B319D6 |
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 | DEFE5FE2AEB188693B6317665FF54662 |
PackageArch | x86_64 |
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 | 69CBB2687D355880F1DBBE529428B4DAE24037B6 |
SHA-256 | D1062951B1B9ABB5A205877EE17E23037FD9278782BAE8B150E7830BBA93F5F7 |