Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 10744 |
MD5 | 10FFC76A97D5EB601E2AD4850D73AEAF |
SHA-1 | 7F4268A9C6B7BA5E0CE162570AF741A4C7DC2F4A |
SHA-256 | CF8328A388CC67F4B84DB98F2C49143179A4D19BA7CB5D25320F24306B872C82 |
SSDEEP | 192:R5huBwOdBz4xZBpR5sdA6LKfif9fYsf/fGW7lSVdKisHJVt1OS:5u/Bz4xZBpR5sa6+6FRHe4lsdQJFOS |
TLSH | T1C1228399BB13CE3FC9588638A6F7CE7477B2C0991B9056832698E03418873DC1F66E1C |
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 | 06A06D59C58A90948442E40A50D0AE06 |
PackageArch | x86_64 |
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 | 64588C136F17D193F760A4D5938F8F8E7E958F54 |
SHA-256 | 82E27237686171B812AEE7903C11EC4F8DBDB6544E419758FB0FBD61731044B0 |