Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 71696 |
MD5 | 0C6F958ADF878F8EA197FBFDBC5A6B35 |
SHA-1 | B1F3477CFAB06FDE3C1DAC6966AA79C0544F16A6 |
SHA-256 | B84EE0129EA9233A2F54C7C818917C847AE7F05E811C151D60DBCD36FD13576E |
SSDEEP | 96:077BB+B72RofWNGwpHzIGUNe3x3S365383Hj33GIZ4OSD9yvvS:0fBwh2GfQbjd66V4HjnvS |
TLSH | T17B63FD44FB13CE2BE158C63896E7CE61B377D46467829B837288D1B42D472C84F62E9D |
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 | 3860427061B54C4B6507A85DD445B401 |
PackageArch | aarch64 |
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 | CentOS Buildsys <bugs@centos.org> |
PackageName | ipset |
PackageRelease | 1.el8 |
PackageVersion | 7.1 |
SHA-1 | 3AB2993AA794D30DC44C142616584FFDCEB8B4DE |
SHA-256 | 979928665E57D4A33024AE2098579D051CAEAF505E6E0BF20006647D74956581 |