Result for 374DA840505304372F6EDCB939B3462ECC37C8E7

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/android/libssl.so.0
FileSize422584
MD5BCA2D10AD82E2B75A108E2D4564FA8A6
SHA-1374DA840505304372F6EDCB939B3462ECC37C8E7
SHA-2562849483D48829CC7D0C830B00A23DE0355C71EB4D58443518F4258752741D92B
SSDEEP6144:43eFhaY4PouroLlkhDTVx1KWx2y3IpSJoiQnZRP6a446LTY:QYrpLqzrm6MSOxwL
TLSHT1E094F953B5E61CAECDD1CC30C22B9521F63874945226AEBF2794FB302F51B58AF1D2A4
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
FileSize676048
MD5AD7F905C12E368D4D613BD67AD375483
PackageDescriptionGoogle's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion13~preview2-5
SHA-1C49591E8FD10A27EDA4343F28B2490CB111C6E25
SHA-256529FDCB974F401EDB4244967FC3909F84B6562AB01D7D2D81A2CADD2C5B67B4D