Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_net.so |
FileSize | 14496 |
MD5 | BD4FFAFAFAC75EB78510890F8E37B6F9 |
SHA-1 | 255316C9245A1352C8593EE4F4903818661D9185 |
SHA-256 | 8B359B1BE164FB3FB83E6EBF0EFF46EC85E209BFE264848FF5007FA664A9A814 |
SSDEEP | 96:9nQBWBfYC6iTJIEy5iM6Kg8Mgk99cIQjdCjl:S8lYCkEpM1ccIQj |
TLSH | T14552CBDBEE04DA3AD85806F0C89F07E3B361809686838F036D24F2457E533D5BD66DA5 |
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 | A6003C529B21F9547ECBF860DB298C94 |
PackageArch | aarch64 |
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.mga7 |
PackageVersion | 7.1 |
SHA-1 | 63B45A9E290613A8865FB7EAE083F74D9558BD07 |
SHA-256 | 2B3FF394816845B8DB7CB0F5E1F976E282BF399996A0AE8F3CB70261C9778C8E |