Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_ip.so |
FileSize | 17784 |
MD5 | A3F7D2AA371FD01291AEB1FA12F39E5D |
SHA-1 | 5003F84A6F421AE76C5D8484646E1D608208AD4D |
SHA-256 | 2719522E07E669AE750C14EE7A54331CFCCE0209058B20F43AD40D704F02D75D |
SSDEEP | 96:RmlBWBSYO9Q5dpiI3g/ehRHzXr7kfBf47Eo33VvyttBXney:wl80YO9Qn/3PLzXr7kfBf47EsGtB |
TLSH | T18E828557EBA0A97FD0BA877460CB476272F9C46516E3029B29943218AE632D05B31FC6 |
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 | 2C94E3CDC6CBFF9F56CF41E48757DF98 |
PackageArch | i586 |
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 | 676CCE452946940F76B19260F78CC29FCCF35672 |
SHA-256 | E96EC123971C9D0545E4BADB49807041DD6DE976AE165FEED8EFDAE3D6A544E6 |