Key | Value |
---|---|
FileName | ./usr/sbin/ipset |
FileSize | 14652 |
MD5 | 3AD7F5496C50DA7E86E9E476C5238051 |
SHA-1 | 288B3608DC124BD357B4865F81DE3F4F3879BAEC |
SHA-256 | 83C8E590EE245C2DA014EC9A4F9A8209A61ED48EAE82C51B75DD21CF218396EB |
SSDEEP | 96:f8SceGqidPSl/M7t4ojKjkIHBWr1Z8EjBpCFi:fxLidPc/e4FjkIhaeEt |
TLSH | T12F62E710F385C9FBD8A3133884875BA523B1F411A0DBEF633A0473526DA57986917207 |
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 | 0CE2CB25D0B4DE8EC381884705E88585 |
PackageArch | i586 |
PackageDescription | IP sets are a framework inside the Linux kernel since 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. ipset may be the proper tool for you, if you want to o store multiple IP addresses or port numbers and match against the collection by iptables at one swoop; o dynamically update iptables rules against IP addresses or ports without performance penalty; o express complex IP address and ports based rulesets with one single iptables rule and benefit from the speed of IP sets |
PackageMaintainer | luigiwalser <luigiwalser> |
PackageName | ipset |
PackageRelease | 1.mga8 |
PackageVersion | 7.15 |
SHA-1 | D99976BFD084E77E0B4AD98A11855360F36CEF47 |
SHA-256 | E66DF470409AF3CFA06846C78A3C8B19C3E6F065D4B8996F880EE92CDC083730 |