Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_ipportip.so |
FileSize | 19024 |
MD5 | 0FFF08097D95A53A9A171057D0C1C2FC |
SHA-1 | 04EAE44045C30E854DC6E59535DDCAA594108197 |
SHA-256 | 5E76B72A939AAE29557E45E02E6E6472D1E778F2CD30A06AE2B933D0606F5DD3 |
SSDEEP | 96:RnIxBWBf7/KkSguTeuOuXYm2cpV8Ng/OzsNMTCHIbiVv/ZINylix:RA8p7/KUu8N74NMTCki3I |
TLSH | T1A4820C56FBA1A92FC4BC4778509B8730E3B4D051A2F3432365181B689E432A46F76FE5 |
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 |