Result for FE44F2AC3D08643DB4F54240020BE9D8EC28A872

Query result

Key Value
FileName./usr/lib64/liblognorm.so.5.1.0
FileSize156544
MD5A4BE00546A84C87E59E03ED1BEAF9E81
SHA-1FE44F2AC3D08643DB4F54240020BE9D8EC28A872
SHA-256915101F1CE95B3C2F1B1E2F150EF45C6B4FE2432517AA47BDEAE9C1E8AEA88BD
SSDEEP3072:VU2Vp19R/R3fJGcxh8ZVJr6EbGgTCiFZVsnrHupOPz:289/oOh4r6n/YZVsnrHupOPz
TLSHT1D9E34C57B2A614FDC1C5C530469BE2627DB1F46187226A7F24C49A713E42F381F2EF26
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
MD5A70161C9EBDACE8506504CA325C05169
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.
PackageNameliblognorm5
PackageReleaselp153.51.10
PackageVersion2.0.6
SHA-11065AC38CFBEC1089CF468132785679F01913003
SHA-2565DCF3BE7E49227CC7318E0589B33BFF74C8760E6DAAD80B40EAEAE279EBE69BC