Result for 3FBCA0D7529C49E515AEDA4D981AF79845AC7276

Query result

Key Value
FileName./usr/lib64/librelp.so.0.5.1
FileSize104280
MD5C2B70C58D3B1A0F4D1E27974392D1C80
SHA-13FBCA0D7529C49E515AEDA4D981AF79845AC7276
SHA-256FDDA456F82EDDBC16C3F2EB58764FAAC331F540827B96810684E2F6486E02274
SSDEEP1536:KSxIkbzRxCzvNpWl+yNI0OuRVhpf3LzG5JQTq9PAbEe:Kj84jWl+MI0OuR5LzOKUPKE
TLSHT134A31947F62586A2CCF06637E51B5AB387FBB03266C4741CBEACDB1E4C917009778A61
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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
MD5B26323ED42F8702F69A714332A55BB5A
PackageArchs390x
PackageDescriptionlibrelp is an easy to use library for the RELP protocol. RELP in turn provides reliable event logging over the network (and consequently RELP stands for Reliable Event Logging Protocol). RELP was initiated by Rainer Gerhards after he was finally upset by the lossy nature of plain tcp syslog and wanted a cure for all these dangling issues. RELP (and hence) librelp assures that no message is lost, not even when connections break and a peer becomes unavailable. The current version of RELP has a minimal window of opportunity for message duplication after a session has been broken due to network problems. In this case, a few messages may be duplicated (a problem that also exists with plain tcp syslog). Future versions of RELP will address this shortcoming. Please note that RELP is a general-purpose, extensible logging protocol. Even though it was designed to solve the urgent need of rsyslog-to-rsyslog communication, RELP supports many more applications. Extensible command verbs provide ample opportunity to extend the protocol without affecting existing applications.
PackageMaintainerhttps://www.suse.com/
PackageNamelibrelp0
PackageRelease150600.16.2
PackageVersion1.11.0
SHA-1295F8900E01C8D12942B8CEF1F2A181603358C42
SHA-2560A0BB33BCBBA919F156E8DD1987AEF214B6C3138D277E6958D43FCE49945DD6B