Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 71696 |
MD5 | 245F9DE34F39633A16006917E8CD9140 |
SHA-1 | 615772B43A5413B4C5E208DA6B8BEA06FAF86645 |
SHA-256 | 6A06C534C779024C1810194BD3F3BDCEB0FD35C51FC749FF9EBF49ED8C91E82D |
SSDEEP | 192:mybmBwDnvMewxqLkl3699/iGrYT3TxsFzNqHSt:fbmSvMewxqLklq99/TrYTjxsFzNH |
TLSH | T15E6376A67B639B2BD514C93852B7CB3473B0D95D078193433694E27A2DC33B88F26B49 |
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 | 7CC2B388BA22B97FBA5E1C902AAFADB2 |
PackageArch | ppc64le |
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 | 22206F0F1628E86C319E7295FFDCC4F99857F832 |
SHA-256 | DC71FA093B472BF0D59AB44F6F824592BB0E8FCCEB88035E980D91AA2626F826 |