Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_netportnet.so |
FileSize | 13504 |
MD5 | B511F42F6852329E17137FB758F228C6 |
SHA-1 | 2087A0893FE5569AF86AB2B4AADA5792A4C92D69 |
SHA-256 | EA0EA11AA4E4EDC8BFB256238143B0CD63A84A8A6CE1371B72A455F59B7C78E6 |
SSDEEP | 96:adxBWBA7nOntLPJTpJgUF62NLsSPeaL9xDrkrV+ArfKt0dWx:aH8+7nOhPdb5F62NDPeaTrqs |
TLSH | T1FF527356EF91DE3BDC9C0B7458AF0F72B360C1CD2A9683632139A3417F072E61D6108A |
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 | 4951BFB849B7AB20CA71329816844CC8 |
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.mga8 |
PackageVersion | 7.15 |
SHA-1 | 6329FDF9F2619A1600591F46E5CBE944CBAD030E |
SHA-256 | F84B261D79B3E2712648150A8CEB0C02A5C743B6AE89C8D50A19DEC55A172093 |