Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_netport.so |
FileSize | 20280 |
MD5 | 23C2E23C7B8E27C49714C97D77092AAF |
SHA-1 | 0BF388649119D0A13B9EB153F567F5F915239364 |
SHA-256 | 19F38BB9B28ADD5D262572F3E012824CDBCC782F92698E87DF4919BDFBF148C0 |
SSDEEP | 96:RA44BWBb7H3IYueuXmcPNa5R1Org/eNzEb5j6+iVvIxBIck:RA8R7H3HVhUPNgbbi+/ |
TLSH | T1ED923D95FBE08D6FD03C577451CB0F36A2B8C094A2B743179AB49A295D176848F33BD2 |
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 |