Key | Value |
---|---|
FileName | ./usr/lib64/ipset/ipset_hash_netport.so |
FileSize | 24400 |
MD5 | D6D31F1DA22594E5500730A0B72D01CB |
SHA-1 | 0F15215D18BD167992D43926700C6AE879D3E281 |
SHA-256 | B2B78E021AEA97182F6FF5CB6796829C1B3119AC3118C6D1A5181A93D0DEAD5F |
SSDEEP | 96:RMt5AxBWBb7H3MC1N/+xn2sfda5R1Grg/eNok5C3s3biVvuSFv4:Rl8R7H3J1BhcPNl5Ji |
TLSH | T15EB2FA12EBE1892ED0388B7451DB4F37E7B8D65073B743079AA453265D13288AF23BD6 |
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 |