Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_ip.so |
FileSize | 9500 |
MD5 | B03B74B1CDE59DAE1A51F941A6901E94 |
SHA-1 | 36A64E9C29B7215F001B0494A2D6901FA2C760A3 |
SHA-256 | 66787730432BE169E3EFE93920497B015B4E1C901B8D63CFBF3662CB9EBEB598 |
SSDEEP | 96:PSPBWBShKAzuhg/eF+NYSQCl5KWLRPIizVx6UI0:i80hCPgNYSl5Koe |
TLSH | T16412228AF7A05FBBC058913571DB0692A376D93C21D30353A98862247F651AC1FA3D9A |
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 |