Result for 6BE851DBEDE6C5BB956BDF5E9FDF99E2A78A3877

Query result

Key Value
CRC3214B8AA03
FileName./usr/share/doc/packages/librelp-devel/AUTHORS
FileSize54
MD5EF15779112E2E1122F1C181E624C82F7
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '80648', 'OpSystemCode': '51', 'ProductCode': '183361', 'ProductName': 'Scientific Linux DVD 2', 'ProductVersion': '6.9-i386'}
SHA-16BE851DBEDE6C5BB956BDF5E9FDF99E2A78A3877
SHA-2566FA4FD848619B764B9505AFAB190E7C950628113C552FC7D8BC83AFF8D344ECF
SSDEEP3:1uFjXU2NLEkKLYFIMO:wQ2NL/TO
SpecialCode
TLSHT1A4900258490491226156285493033C6156112BD75125896080660985B24D0837206890
dbnsrl_modern_rds
insert-timestamp1647017929.7002194
sourceNSRL
hashlookup:parent-total402
hashlookup:trust100

Network graph view

Parents (Total: 402)

The searched file hash is included in 402 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5E257D5E737A7F551114640F815E777D7
PackageArchx86_64
PackageDescriptionLiblognorm is a library and a tool to normalize log data. Liblognorm shall help to make sense out of syslog data, or, actually, any event data that is present in text form. In short words, one will be able to throw arbitrary log message to liblognorm, one at a time, and for each message it will output well-defined name-value pairs and a set of tags describing the message. So, for example, if you have traffic logs from three different firewalls, liblognorm will be able to "normalize" the events into generic ones. Among others, it will extract source and destination ip addresses and ports and make them available via well-defined fields. As the end result, a common log analysis application will be able to work on that common set and so this backend will be independent from the actual firewalls feeding it. Even better, once we have a well-understood interim format, it is also easy to convert that into any other vendor specific format, so that you can use that vendor's analysis tool. The liblognorm-devel package contains libraries and header files for developing applications that use liblognorm.
PackageNameliblognorm-devel
PackageRelease51.58
PackageVersion2.0.6
SHA-1005D34FB5A36732A2D0BF7B86230DF029F3CA2B7
SHA-256040BE856C18A17C958A75DCDBF81DF64899F1B9A202464B7C4FF5C722526889D
Key Value
FileSize47720
MD5F389FA0A451646D09FA6410E395B5204
PackageDescriptionReliable Event Logging Protocol (RELP) library RELP provides reliable event logging over the network. . 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.
PackageMaintainerMichael Biebl <biebl@debian.org>
PackageNamelibrelp0
PackageSectionlibs
PackageVersion1.10.0-1
SHA-1015E724C548AAA0FA152382B945D69B51E7B267E
SHA-2561629400716D1C3BAA03BDC73574778B54135D79ECBBCB787AD1A35047787D6A5
Key Value
MD5927483164DC942D23A3E6B739BE504EF
PackageArchi586
PackageDescriptionThis package compiles the string handling essentials library used by the Rsyslog daemon.
PackageMaintainerumeabot <umeabot>
PackageNamelibestr0
PackageRelease3.mga8
PackageVersion0.1.11
SHA-102F6ACEF19ECA884C93D9012C4C375502AF1C6FC
SHA-256970929C75D1C083A98A7ED024CA2A3170B40BA4F3470BF8A6CA3EBB847C1EF7A
Key Value
FileSize43098
MD5134E67A3BD008F37ED88D00F2CAE70A8
PackageDescriptionReliable Event Logging Protocol (RELP) library - development files RELP provides reliable event logging over the network. . 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.
PackageMaintainerMichael Biebl <biebl@debian.org>
PackageNamelibrelp-dev
PackageSectionlibdevel
PackageVersion1.2.12-1+deb9u1
SHA-102F9603521A0F777CC62BEA9B3574EE5ECDB360F
SHA-2560FF7B713A4BB78153E076859C80BD7D4E26E8626C6D3FCEE8CD0EA11982E9932
Key Value
FileSize53436
MD5AC28F835FB140C5A5C8AFA1910619466
PackageDescriptionReliable Event Logging Protocol (RELP) library RELP provides reliable event logging over the network. . 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.
PackageMaintainerMichael Biebl <biebl@debian.org>
PackageNamelibrelp0
PackageSectionlibs
PackageVersion1.10.0-1
SHA-103841204BA1B12F4C7D5829FF106311F032602DD
SHA-2568762580DC38331DD13DAEC6180AFE09EEEBDA390394283817083C912229D869F
Key Value
FileSize50414
MD5CBE99FD5AFDE9A50FA69BE47EFD26F42
PackageDescriptionReliable Event Logging Protocol (RELP) library - development files RELP provides reliable event logging over the network. . 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.
PackageMaintainerMichael Biebl <biebl@debian.org>
PackageNamelibrelp-dev
PackageSectionlibdevel
PackageVersion1.3.0-1~bpo9+1
SHA-1051A585F213C04F644232A850DCB88608E99336D
SHA-256FB9A632E17619CEE0EB56C7DC42459C4D4FF739A1599F71922FFBFC9CBC3DCC5
Key Value
MD5AA72CD100B5463E4577BF4633743BA6D
PackageArchx86_64
PackageDescriptionLiblognorm is a library and a tool to normalize log data. Liblognorm shall help to make sense out of syslog data, or, actually, any event data that is present in text form. In short words, one will be able to throw arbitrary log message to liblognorm, one at a time, and for each message it will output well-defined name-value pairs and a set of tags describing the message. So, for example, if you have traffic logs from three different firewalls, liblognorm will be able to "normalize" the events into generic ones. Among others, it will extract source and destination ip addresses and ports and make them available via well-defined fields. As the end result, a common log analysis application will be able to work on that common set and so this backend will be independent from the actual firewalls feeding it. Even better, once we have a well-understood interim format, it is also easy to convert that into any other vendor specific format, so that you can use that vendor's analysis tool. The liblognorm-devel package contains libraries and header files for developing applications that use liblognorm.
PackageNameliblognorm-devel
PackageReleaselp153.51.10
PackageVersion2.0.6
SHA-1060AFFAE732EEA8C6B71851AE38BF56693FA29E7
SHA-256672ECE527F9784F412E18DD2191086A105B152B59B57C28E5DBA0B55A2020F0B
Key Value
MD5B32631FB2A12B4F06C1315FAD050E142
PackageArchi686
PackageDescriptionThis package compiles the string handling essentials library used by the Rsyslog daemon.
PackageMaintainerFedora Project
PackageNamelibestr
PackageRelease14.fc32
PackageVersion0.1.9
SHA-10671A6A7B85910C5CB67ED26D5772C7D236F1BE0
SHA-2567CCFF08D312BC45BF12C5858BE1720A9ECE5EBCBEEE1E46AD9E24205DFF13940
Key Value
MD536237351EBCCFA1679870DB9EEA75546
PackageArchx86_64
PackageDescriptionThis package compiles the string handling essentials library used by the Rsyslog daemon.
PackageMaintainerumeabot <umeabot>
PackageNamelib64estr0
PackageRelease4.mga9
PackageVersion0.1.11
SHA-10678DF0E95A7764F0F0E52B978068314FCBA7CCF
SHA-2561C389446195AFA236FE39D49C70B69EB85AD32779232AFC5622826F6F7FC2B1F
Key Value
MD561051D1A0B75F2E046520A2F49417FD4
PackageArchx86_64
PackageDescriptionBriefly described, liblognorm is a tool to normalize log data. People who need to take a look at logs often have a common problem. Logs from different machines (from different vendors) usually have different formats for their logs. Even if it is the same type of log (e.g. from firewalls), the log entries are so different, that it is pretty hard to read these. This is where liblognorm comes into the game. With this tool you can normalize all your logs. All you need is liblognorm and its dependencies and a sample database that fits the logs you want to normalize.
PackageMaintainerFedora Project
PackageNameliblognorm
PackageRelease9.fc32
PackageVersion2.0.3
SHA-107260EA14C2BAC05EA84CC6083E21264CC28E36F
SHA-2564AC6A08305928AAD8D608648168F4B541418FF84D39A78AFC9D3916C4A988EC8