Result for B4CCD2596A2C08323C8585D58E2BEFCC034C4F4E

Query result

Key Value
FileName./usr/lib64/liblognorm.so.5.1.0
FileSize156536
MD522F847565013A00D171FB0D279F20AD8
SHA-1B4CCD2596A2C08323C8585D58E2BEFCC034C4F4E
SHA-2566D223C81B43A2D7C016EE52492D9F05D1A8D309961011EB7D013146291042691
SSDEEP3072:e7AIgumZRXqRosR38ZFwrxgmgTjbCqZVkCpnuZt/u:e7Hgtj+3lrxpybZVkCpnuZt/u
TLSHT1F2E33B57B2E604FCC1D5C430469BE26279B1F4A187226A7F64C49A713E42F781F2EF26
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