Result for 25A1CA3473FBC55190534FE5B889F394AA915A92

Query result

Key Value
FileName./usr/bin/lognormalizer
FileSize18968
MD525CDC43269C4678E7B62438C0F364568
SHA-125A1CA3473FBC55190534FE5B889F394AA915A92
SHA-256A33A0C0E9117BC68E2B71E9AD620E731858B328FA8A988946381A8E5FF314921
SSDEEP192:R0SawMLIutKefBP6kpsXlRZdL3EJ6IQZ8QfEU/Aloi:CIutKWpDpsXL326IQ
TLSHT11382C50BF7014A7AC5A80BB485CB452425B6A84AEB32A71F748CF1707F41B685E2F7D9
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
MD599FC390EEE33D77DB33ED746F98F0156
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
PackageRelease51.6
PackageVersion2.0.6
SHA-108E2A7BDDCEB982C8DC4EA49B017CDC2B2FA7DE5
SHA-256FB1DC2B0F55DE1BB8073E14155C34A4EBEE7BDBF1C75835FF6AB9A4112086D8A