Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_ipportnet.so |
FileSize | 24408 |
MD5 | F521A9D043C84FABAF7F764F1734306C |
SHA-1 | 11C7062479423A5604921A30FF5983AF59ECFC97 |
SHA-256 | 4D69F6B21F556B8AEADFC4BE48311BF7ADB8A2DDF3AC3C0848EE560CEB969B35 |
SSDEEP | 192:R28t7WQW9Ahu54N/6y6x6f6U6Z6O60c5ni:w7L4N/6y6x6f6U6Z6O61 |
TLSH | T1EEB24317EBD3DE0EC4BC4634E4DF477FA7B4D9A466134313AA181A250D432E09F2A9E2 |
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 | 15360458A078A3B7D534C09260722951 |
PackageArch | x86_64 |
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 | 5EB986D0B7542D7059846C7AE2920C38275A71D9 |
SHA-256 | 0A09AE07FFD513803C05DFBA48365523BBB300B02FF2F47627BC44B003045A58 |