Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_netnet.so |
FileSize | 17736 |
MD5 | 7D5A3AC814FE44A8851511DEE45C6D68 |
SHA-1 | 06FB863058141CE156A9AC99EB2B5D338FD63FE5 |
SHA-256 | 3A51DC888EA4C942709D2FCDF72BD64D0AE30668706A76946E1023673A146F63 |
SSDEEP | 96:Reou+yBWBwXUbFHfodSMkKgZj1AXg8MJ+OufPiWbiVvqw8yllW:Rpy8+fjgZ1G2sPXi |
TLSH | T11C829486EB90CB3FC5B8473008EB4B32B2F1D454567203571B3857293E637941B3AAE5 |
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 | 15360458A078A3B7D534C09260722951 |
PackageArch | x86_64 |
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 | 5EB986D0B7542D7059846C7AE2920C38275A71D9 |
SHA-256 | 0A09AE07FFD513803C05DFBA48365523BBB300B02FF2F47627BC44B003045A58 |