Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_netnet.so |
FileSize | 8372 |
MD5 | F3B295554DA3FCDF6C4488FC45055645 |
SHA-1 | 4C01C4BA854EB4DE96C883972DF1C006314E0306 |
SHA-256 | 5EE7EB04B6F9F790B3CB1E2D9BCE58F44A7A2F2A9A26B6296B87416C77539B17 |
SSDEEP | 96:WRyBWBw+DXWV8p9g8MJQOLFoTHbgLzVIfU8:/8++yq2VLFoX |
TLSH | T19E02658DE7905FBBC0544634B1DB0365B377C96D265243569B8C42223F3A5B80E66B1A |
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 |