Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_bitmap_port.so |
FileSize | 9368 |
MD5 | 94AA19B9082066925EB5B34186ED3F15 |
SHA-1 | 2256023505259DE7190CE143002040EA4CC4CAE3 |
SHA-256 | 6137B234DD8C603E8F268B80279DBE2D0D9725C176F06AD99FE67508A7E4AD2D |
SSDEEP | 96:vBWBno/6L6MTkoLbXcGbAP+ArL99t0lN:v8+/1Qk2 |
TLSH | T1CA123F8EEFC8FE6FEC7C5B3554EA037273B5D95A9A51C323621803617E432E81E21185 |
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 | 7218561E088DAD393EB1DCD6ADB7B8D7 |
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 | umeabot <umeabot> |
PackageName | ipset |
PackageRelease | 2.mga9 |
PackageVersion | 7.15 |
SHA-1 | 169EDE391FDDA458380E2DE4CAE9A51A26EBA5B4 |
SHA-256 | 22B5832B25E6E5A2A4946D4DE8564CCEC5298BE8013559FE6463E96A1189B898 |