Result for AC857FDE04B3BA49546F5BFD050B833B0EF635AD

Query result

Key Value
FileName./usr/lib/liblognorm.so.5.1.0
FileSize142836
MD584B4E42FB308A2C790A0A5848924B4CE
SHA-1AC857FDE04B3BA49546F5BFD050B833B0EF635AD
SHA-2563535CBF2E4DE792DBCEC0EB285F09B967192027C19BD1273B90761193AD499CC
SSDEEP3072:CFZ2s/RE7GcX2N94V1d+4pJhiCNOJVK/N2phYI:Ce4RkF2MV1dp1GVGN2phYI
TLSHT1A9D32A97B841DE91C5C026BABB4E435933670B74E7DE721AC904CB303FD69DE893A684
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