Result for CC29D486F8E0FA36CB901FF3C1E9EC159A7837F6

Query result

Key Value
FileName./usr/bin/lognormalizer
FileSize18976
MD597EECD11AF6A3DFD57A6FE521EBA284B
SHA-1CC29D486F8E0FA36CB901FF3C1E9EC159A7837F6
SHA-256E2A6B266A0A0D5AD1BDC4469466097B1BFAC4B522E9A219C06EBF391C4381DED
SSDEEP192:R8MpwMyItt5/6gRTZlT+zlK693EJ6IQZ8QfEU/A0oi:mIttBvRLT+zZ326IQ
TLSHT19182C40BF7015B7AC6A80B7489CB466066B6A84AEF31661F348CF1706F51B984F1F3D9
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
MD5DAE1A680735CD4712BBE7D185A8837E3
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
PackageRelease150400.51.1
PackageVersion2.0.6
SHA-1072109A9280C7C5C946034F3E07895919CB2A8AE
SHA-256C96C1C8D7495022103A426A728071E1C6E987AB5159CE8C1A88EDF0E0B833055