Key | Value |
---|---|
FileName | ./usr/lib/ipset/ipset_hash_netiface.so |
FileSize | 19408 |
MD5 | 6A34443891685C9ECC43A65F33F6E0C7 |
SHA-1 | 388C145E4F1219A6582CF4D939E3E01BEFC42456 |
SHA-256 | 117B6E9B17B88566D5241291DE3597C933F21E875CADE5E4F630CFEE3E0987C4 |
SSDEEP | 96:f/s9P+DBWB40YcSJdeVcg/eFH/gTUk3L1x23VvSpeTneUl:ns9GD8G0YLNPF2l34P |
TLSH | T1B692A78EABA0DAF2C0739734B1CB871371F2C06147A5135B2CA809A6AD1B3D50D31FE6 |
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 | 2C94E3CDC6CBFF9F56CF41E48757DF98 |
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 | luigiwalser <luigiwalser> |
PackageName | ipset |
PackageRelease | 1.mga7 |
PackageVersion | 7.10 |
SHA-1 | 676CCE452946940F76B19260F78CC29FCCF35672 |
SHA-256 | E96EC123971C9D0545E4BADB49807041DD6DE976AE165FEED8EFDAE3D6A544E6 |