Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_netportnet.so |
FileSize | 17720 |
MD5 | 2693DCFFF8FF567AA5D74AB9E7B01BD3 |
SHA-1 | 0AA83078191DFE31B1E6BC54957004F52A729ABE |
SHA-256 | 66CB997EC6112B79D7AAFAE248AA17AE19205F420FB2C9B15673BB72A32DCE80 |
SSDEEP | 96:RiohBWBA7nODWguTeuOuXYUZj14bmgUF62N+UCCq/i37n+iVvvBIx:R78+7nOvAZ1465F62N+UCCq6yi |
TLSH | T173826046F781DD2FC47D0370449BCB32BBB2E15093A28323A51496685F13B982F22ED2 |
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 | B5C0CE74EA1F421D437C7DB4EE39F371 |
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 | wally <wally> |
PackageName | ipset |
PackageRelease | 1.mga8 |
PackageVersion | 7.10 |
SHA-1 | B6192DD86D31BA5D2BDC00372A48D88D82727F9D |
SHA-256 | 8CFBC28FF15D3E8B8F08C9CC8ECFA2F06CC06E141E1D800F51510D6539504585 |