Result for E14578E19E38ACB7479C37ACD4A3027FAA8213AE

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libssl.so.0
FileSize255516
MD5716976723979206C00EDBAAF66B7CD89
SHA-1E14578E19E38ACB7479C37ACD4A3027FAA8213AE
SHA-256FDF228FFBBE01970E5E69FC196B4C8F8D1C31A47F882DB6FE6076C22EBAAAD8B
SSDEEP6144:2EAFlEFQgY0aYPyu96yvpxAmQqxhAZfoEqGVBzn3F1m2awd:PYWqdyvHAm0ZA8n3K2j
TLSHT1BA44AEC7700F1887C4C689FBBA738AC2806AE1C4A7D58F03375855353E7A9AC593E6E4
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
FileSize494984
MD59443336D1892E8E3924F6F2CCD51CD64
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
PackageVersion10.0.0+r36-2~exp1
SHA-1250A7DBE49E19693F59F10A87B08F9BACC4A1550
SHA-25649A0D874D220F3E4C702BB2BCD322CC950FBD9267A80B401E1EDAD5908DC2DDE