Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 69200 |
MD5 | DA2CAB200B824B65F465EFDBF035A041 |
SHA-1 | 5325D0BFB2CA37200B2E82DD95C666ED9B583EDE |
SHA-256 | C5967FE092A799A1B24361D2472BE2BD2885E5A7B9D80ECA70CBA85F83A7FDC5 |
SSDEEP | 768:YvaFtA4z1xxK/YtiwpLQHK0P4+vtMyrQtr:Y0tAexE/YtL2JMyrQtr |
TLSH | T17163E8C377845917D2901FB045F537B8E76E64D21A29620B790F036B4EE1AC0BE7E78A |
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 | 87520A973AA0B0ACC644F2EB10559B0B |
PackageArch | ppc64 |
PackageDescription | IP sets are a framework inside the Linux kernel since version 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. If you want to: - store multiple IP addresses or port numbers and match against the collection by iptables at one swoop; - dynamically update iptables rules against IP addresses or ports without performance penalty; - express complex IP address and ports based rulesets with one single iptables rule and benefit from the speed of IP sets then ipset may be the proper tool for you. |
PackageMaintainer | Fedora Project |
PackageName | ipset |
PackageRelease | 2.fc24 |
PackageVersion | 6.27 |
SHA-1 | 16A7049EE811F7F9367F0935B34E7B105C262A53 |
SHA-256 | 4573AC8E3FC07697911E5D69E68445AF4322E15D9044E538A89EDAA49F3B08E0 |