Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_ipportip.so |
FileSize | 17780 |
MD5 | 8BD2BE8A48A9AC6DA023C66B8577E4EB |
SHA-1 | 4FE87010C3986E6447EC59BBDAB0CA506BDEA182 |
SHA-256 | 09398132478C3750D5D4528CD9662A3E20DAB34D2EA6711FFE7E0735437DB2C1 |
SSDEEP | 96:ffgBWBf7/KYbIlvLplaFLELg/OzsNetM7fCJoVvVgTumvrW:Xg8p7/K5ld9L74NYM7ffoR |
TLSH | T1DC826256FBA1AA33C0BECB38509F5731D3B1C4A192B7835328581988BD132B09936FD6 |
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 | 9FCD4ABEB255753F2C767A19154DCA66 |
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 | umeabot <umeabot> |
PackageName | ipset |
PackageRelease | 2.mga9 |
PackageVersion | 7.15 |
SHA-1 | F481698349968EC8F7880A3FFE00F2C1BB86A522 |
SHA-256 | DAE7ECA01009917F52E0CF996BA6F9A4D665BE3AA9C058A3866476ACDEC6AC42 |