Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_netiface.so |
FileSize | 16624 |
MD5 | 7D5C6D14C13DD13EA21213262967D759 |
SHA-1 | 322E1F334AE3DB10148AFA99E8B2BCAA6A6AEF8D |
SHA-256 | D6920B89B2F64B0303D0DE02D3924FF9BCA05BD37789BF6BD027E4D5B8A83469 |
SSDEEP | 96:jtBBWB40Y1kdBXtzRjBuo7c6DU9g/e9t6w8uTQx+ArI5d0VI:pB8G0YWdBdHuow1P/zTQIx |
TLSH | T12372CB5EEF80E8BACED84B34A48A0F5733B7C460D2918727152C53667F4B3C55EAE681 |
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 | CD5FCB5A344A9455EDCED56941FFD2F9 |
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 | luigiwalser <luigiwalser> |
PackageName | ipset |
PackageRelease | 1.mga7 |
PackageVersion | 7.10 |
SHA-1 | 2E8DF5C937B24104EB680C6DA9C8A747922E9826 |
SHA-256 | 6BF5AC5099D7729ED2C3EBB7C77B68010822F71C2ED48D7E0744231121DF1026 |