Result for 35CF761C73DBD9004A9A61353BE33EE175FD6C80

Query result

Key Value
FileName./usr/lib64/liblognorm.so.5.1.0
FileSize160720
MD5CFEC81509B361105510DF2C5199156AC
SHA-135CF761C73DBD9004A9A61353BE33EE175FD6C80
SHA-25681FAA11C86D0A4ECF8975C3A38B632B7A8CB57E64B6B7F26F6CCCA589AFE6CBF
SSDEEP3072:YSYU/VeCHaioWtQjFlKRLAPt7kHaEpsR04Ypti:YfcDH9kjFlKRMt7kHaEpsR07pti
TLSHT1A3F33917B2E614FCC0D5C930828BA2527D72F49297327A7F68849B753F42E385B1EB25
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