Result for C0D81599A00E155E1DD45F49DF9896FF77A5B3E6

Query result

Key Value
FileName./usr/bin/lognormalizer
FileSize23152
MD57B229BEE907DD7121DD36ECF5FD4390F
SHA-1C0D81599A00E155E1DD45F49DF9896FF77A5B3E6
SHA-256A81E3C3915AE6B2B710368A627965F6FE48D7E8FAB2F437A635BCD3729C330A9
SSDEEP192:RQTnOrwcOK9IgGsAVrc/Yicu5jCxMgDFce+iaB/MQMJ6IQZ8Qfdwusvi:D9INsArcIyCFDlAMQu6IQv
TLSHT1A9A2E50AFA605A75C5C04B3044CB477262B1AD82EF32931F70CCB1B11F417A9AB2B7A9
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
MD5DFE3990467015998F2A5CC64548C1C7F
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.58
PackageVersion2.0.6
SHA-10B0DF91F39C54B25CD990069B71A664AD63CDCC8
SHA-25653C5095A9EB98D8EB2EA8B926CFDE3153BB2214AB617C18E8A6537A53382A09F