Result for 1A4C1F982E3967015A44F2A1ED3C54DD7709A28A

Query result

Key Value
FileName./usr/bin/lognormalizer
FileSize18172
MD5A5F0452D0B9AFA8AB8032463CD99BA80
SHA-11A4C1F982E3967015A44F2A1ED3C54DD7709A28A
SHA-256B8B65B4D197CB4E3CEDC8F15C17454DBB27AE47EA7535A5D022554D9C5BB2C49
SSDEEP384:XsHEInbZnfez5o7+Y1oO3hnn6FQ8hly5Z:XsHEC1nGz5o7+a35n6FQ8hlu
TLSHT15482C58AF7C2BE33C6C01679568B875673338095879F2727B55C82782F4137A6DA6708
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
MD5A7B075C4D4BF8C5491D8E48716CCE95B
PackageArcharmv7hl
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-10D8F02D0D50C0B3DFC562BFCA585E2E3734411AD
SHA-256F8D0540D0E52FC31407C08DEA8A3BA54954E4A2A36E2972A1C7AFC98517B383F