Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_ipport.so |
FileSize | 9488 |
MD5 | 235E0DAD84EF6A48F2B38C193FCDF1C0 |
SHA-1 | 4BC8F46DA5B3A1D946E86920F0DF03B2ABF49CC6 |
SHA-256 | 8DAE6A9875AE7B1DF0250578CC0299BBB4D3605ECE23C7B68FDCCDEFFB27F40D |
SSDEEP | 96:7vBWBC7n5AKQwHdTFcrg/OINZBIx44B/2uazPYhB/ezVmEGUQ:r8U7n5AGHd47IN3IxkTEhBA |
TLSH | T18712529AABE01DAEC0649334B8C702717376D57C62B283039AD85234AF972A41F73F95 |
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 | 0085A693A641979D9AB2EF5D5A3B1198 |
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 | umeabot <umeabot> |
PackageName | ipset |
PackageRelease | 2.mga9 |
PackageVersion | 7.15 |
SHA-1 | 7E9674E981B9B712F2EF7C86E5F434049C4538FB |
SHA-256 | DD0A6F606C08F79B5886D8FE60EBCEC60246C9AB408CA505B4D4AEDABFE45E81 |