Result for EFAD12B96BD78CAF3A14C097CE3BBD8A532CEDA1

Query result

Key Value
FileName./usr/lib64/pkgconfig/lognorm.pc
FileSize255
MD51FD7CE81EF4CDC93AB6626C6E4280D20
SHA-1EFAD12B96BD78CAF3A14C097CE3BBD8A532CEDA1
SHA-256DA38C9DEA61336E507BF467DAC636C1911D327954C922D78A522B6ACF257CAD3
SSDEEP6:iD5iDn6XYpeAvVAkEDWFRLKJ9qwf60sHjImfNQa6XCn:iGnJUAvjEqzdwf60sHcmaah
TLSHT183D02B68E15D8DE060596D7148C4874404935505537FC56449C9360284D32ADED7BB58
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5E257D5E737A7F551114640F815E777D7
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. The liblognorm-devel package contains libraries and header files for developing applications that use liblognorm.
PackageNameliblognorm-devel
PackageRelease51.58
PackageVersion2.0.6
SHA-1005D34FB5A36732A2D0BF7B86230DF029F3CA2B7
SHA-256040BE856C18A17C958A75DCDBF81DF64899F1B9A202464B7C4FF5C722526889D
Key Value
MD566BAF49673F6DCCAF543B42B9A0D8E67
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. The liblognorm-devel package contains libraries and header files for developing applications that use liblognorm.
PackageMaintainerhttps://bugs.opensuse.org
PackageNameliblognorm-devel
PackageRelease2.13
PackageVersion2.0.6
SHA-196DBE4F7CEDC10747264686CD7E32B3451106465
SHA-2567B956CF9704D3B4CC6B38391DDF0E5E9FD775CFB0E8FD2863EE4E7E91CD13FDF
Key Value
MD5C209DF987EBA6A12EB98CE86D159BAC9
PackageArchs390x
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. The liblognorm-devel package contains libraries and header files for developing applications that use liblognorm.
PackageNameliblognorm-devel
PackageRelease51.29
PackageVersion2.0.6
SHA-1D5751D1184EF37A5655FC46A2AC35D4F65D3118F
SHA-256977B2F232AF53B2EE0AB57585590F61F27C8DC08F8D5B00C0FAE23642E173746