Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_netport.so |
FileSize | 10612 |
MD5 | D7C421C994D61C34DA7138906C4AF411 |
SHA-1 | 3CFD85A87FE1716A50DA396F5F8FDC316A9889B8 |
SHA-256 | 1D3B5E1C6C8DB499C1E81A9D94402B96FA3DA6B9E840FBD45BC7602FBD2717E2 |
SSDEEP | 96:D1NBWBY7y3KKKUH/FONpNg/eNHwF6DmW7yrooRJzVVF0UQ:P8C7y3KeH/sPNQF6rmsc |
TLSH | T1B6225089BBE41EBEC094873231C719527376D96D32B78313B9AC4232AF171AD0D22B56 |
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 |