| Key | Value |
|---|---|
| FileName | ./usr/lib64/ipset/ipset_hash_ip.so |
| FileSize | 19040 |
| MD5 | 9567377859CFEF64E60A37A5C03AA47C |
| SHA-1 | 2962F15CB47E031097A794AEECFC3753A8D17320 |
| SHA-256 | 56B6DA853C0075B4FFB61EE544BBB93779229EE1A40EDA5B17A87FE6CDDFA4ED |
| SSDEEP | 96:R3oag4BWBSXSHodMvpKA8Rg/ef3PLAERxbiVvSgvylWB:RLg480NrA8RPffb5iEg |
| TLSH | T17A825146EBA0E63FC17C077888D74B7272F4D11976E30393296493396D83AD06F22AD2 |
| 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 | AB9700E6EF3E2FE832F4A2478AB9DF71 |
| 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 | luigiwalser <luigiwalser> |
| PackageName | ipset |
| PackageRelease | 1.mga8 |
| PackageVersion | 7.15 |
| SHA-1 | 58594A116D2269771BEACC73D26864E9681422EA |
| SHA-256 | 1BD5571E430B1906FA4987474505BD5886AB46EF49C32C7FC33718C5D96EBF4F |