Key | Value |
---|---|
FileName | haproxy-1.6.0-sec-options.patch |
FileSize | 1350 |
MD5 | D50AA84706EE2D011FE6CFADF2F53713 |
SHA-1 | 17108F1E159C8F833B8130FE0B2087FF1141343A |
SHA-256 | 82A77581043CF9D29DFE06D9310BF5B6DC0154D6DB46E08B592B406B42D3AEA8 |
SSDEEP | 24:D0xBeT8BhfPxNvJSkTBGmYXL4ZBFulggnGrTYXuQYGl6YXuE3JGxxrGTBs:D0GgBhfJNvJSkUD4ZBFuopOlSE3JjNs |
TLSH | T1CD21BEA7A53E2393D01AD2A0ED19D3899674FA37069DF0FF6010D3F01949F6E919163E |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | D2B47A8029C634CF3E8DC9DFE7794D42 |
PackageArch | aarch64_ilp32 |
PackageDescription | HAProxy implements an event-driven, mono-process model which enables support for very high number of simultaneous connections at very high speeds. Multi-process or multi-threaded models can rarely cope with thousands of connections because of memory limits, system scheduler limits, and lock contention everywhere. Event-driven models do not have these problems because implementing all the tasks in user-space allows a finer resource and time management. The down side is that those programs generally don't scale well on multi-processor systems. That's the reason why they must be optimized to get the most work done from every CPU cycle. |
PackageName | haproxy |
PackageRelease | 1.1 |
PackageVersion | 2.4.2+git0.553dee326 |
SHA-1 | 96D0D2CDB49DE9F29E4E35DAB8E028A115D2CFD9 |
SHA-256 | ADA41C0DC50CDB23BF50AFEF949106E1311475E14BB817806036FA2EF062863B |
Key | Value |
---|---|
MD5 | 15D0D235F37B13F20F5DD4A7468B0A7B |
PackageArch | x86_64 |
PackageDescription | HAProxy implements an event-driven, mono-process model which enables support for very high number of simultaneous connections at very high speeds. Multi-process or multi-threaded models can rarely cope with thousands of connections because of memory limits, system scheduler limits, and lock contention everywhere. Event-driven models do not have these problems because implementing all the tasks in user-space allows a finer resource and time management. The down side is that those programs generally don't scale well on multi-processor systems. That's the reason why they must be optimized to get the most work done from every CPU cycle. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | haproxy |
PackageRelease | 1.1 |
PackageVersion | 2.4.4+git0.acb1d0bea |
SHA-1 | 2C6E1825020A1F1A778E9ADD236AF86A3916A64A |
SHA-256 | 6C110321F29B338867CEBE0E17FC3BA0AAE18E737A18ED164DC91D03DDB73368 |