Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_net.so |
FileSize | 17472 |
MD5 | 8A24861B2435F7E914F3523137B22D60 |
SHA-1 | 490935F524CCD45F9D78B3F26574126D27A3ED08 |
SHA-256 | 94DB7F223368C7F347E4D53C1FE8B71110F700D6DA842AD58C2355F65CCD492A |
SSDEEP | 192:5v8RY6a3pXZ43LUBsnYhsnjhsnussnjsnDsMJMMJ+i:aVk5yB |
TLSH | T109727452FBF0EE32C0F58B38204B075365F2902147EB4B4BB9946154BE236D82936FE2 |
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 | 134513661EA92085A28F281FAC936728 |
PackageArch | i586 |
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 | D5AFBB9DA2911E204CD51FA5ABA14BE5BC59B6D9 |
SHA-256 | AB4CE8AC4B81CD76359F07102236DC46DF231F3F51D719529B0708D7EB220B08 |