Result for BA272E1EC8A06D1F4EF80C87F0B3735E1CAC3BDF

Query result

Key Value
FileName./usr/lib/mips64el-linux-gnuabi64/android/libssl.so.0
FileSize526272
MD55E9D8A152C9C0B3E6B9D1FAA9CB4124A
SHA-1BA272E1EC8A06D1F4EF80C87F0B3735E1CAC3BDF
SHA-25614EB167AA38537400527DCD027B84746A82C5E317FBE9A3A644AB085D18711D1
SSDEEP6144:DWkFMgYSaUEK1nw7ofYJDaDVE4IzBjL4LPafEozjZl0J83dVp:rYgKIYJQVE4IzxL4zafEozjX083dV
TLSHT1F6B4F807AF096E17E4EB8F354C3AD06722BC6CD76240891B7A1C5B8D6D3769E0F8354A
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
FileSize507884
MD59C804DD26D638BC0A9ADFDDABBA01C5A
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-17B21215E599B74E3D47E711B3147007EF21AEE69
SHA-256839103BCDCA294AEB78BB77B8D3BFB88B7931BDC32B0F81947E7A3A6428A4419