Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 6416 |
MD5 | F0560F22F75A82D0B3E5A58FC5096E1D |
SHA-1 | 035F81B27E399E2B0590152D3EE2690AD994092A |
SHA-256 | 6AA4C7A20B932B89687D7EF0F3E9AB0C660D60015D2C7E005E79B0BE80593B45 |
SSDEEP | 96:VfixtxB+BAkiumwdtoScQ/AojLBy07j1oTj8vVEr1Rk0pj2i:xIwKkiiJ9ljL00X1o821e0p |
TLSH | T19BD19346E3A1CDE7C8F14A7C9AB30B54A333D47167974B124A1850B06C5B1A82C92E87 |
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 |