Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 69024 |
MD5 | 2AF718F2A9C5D8D66BC7562A3D6D725C |
SHA-1 | A4788AF8FF7429C1E876F3E6C0E996130F3BCD37 |
SHA-256 | 6D524DAD641C3FF954DE831F326525F5109FCD95A5F2569A0BC0B4E5C70BB434 |
SSDEEP | 96:Cl7kBB+B7YV86vlcevH2qjGuvJvRUnKMoD9KvvB:ClIBwhYVrR9ZrQRo |
TLSH | T180638414FF15CD6FE45987384AE78770B332E855E3528B93B10892753E073D94FA2A89 |
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 | 40A438E15829FF5D7D76659034C12E3E |
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 | Fedora Project |
PackageName | ipset |
PackageRelease | 1.fc32 |
PackageVersion | 7.6 |
SHA-1 | 1F08372033FF350BFB22762EA0B66E1873F4005C |
SHA-256 | EA25C1482716623EABC1B151D318BC1499E2448480F46E6113E1E4667150393C |