Result for 813580C97372FAA278D5E17671D79BF49AC0FF97

Query result

Key Value
FileName./usr/lib/librelp.so.0.5.1
FileSize104508
MD56DCE960B3361D2AD8C384CE16707F5D2
SHA-1813580C97372FAA278D5E17671D79BF49AC0FF97
SHA-25656BC95968E3580B2CFB130B33F452BF680DEE7FE07E42C983FDE1B048748175A
SSDEEP1536:EEei9tXWpp99Wqqh+rbcbrUL0b4kJMsxiFgcMmZw48:tB91W99owP0q4GFgcMqw48
TLSHT10CA33A46F683C4F1F2E110FC966BA7226E24810F8257D3A2FE48775A7978754AF1A334
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
MD56D2AF2402E647A0C3ED1BD679F1449EC
PackageArchi586
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.
PackageNamelibrelp0
PackageRelease91.50
PackageVersion1.10.0
SHA-112C0BA8D21C52F3A61C76D71D841444245FEFB8C
SHA-25619CDD1150C6846FBCDCEDDFE3F6486F52D90016BE099BF0B93F541C19C9DF5CF