Result for 7BC3E87F9D0DB97F1ABF269935913D684DCBEE70

Query result

Key Value
FileName./usr/lib/mips64el-linux-gnuabi64/android/libcrypto.so.0
FileSize1330128
MD582B7B53C12DBF80DB7E94589DB0B4AD1
SHA-17BC3E87F9D0DB97F1ABF269935913D684DCBEE70
SHA-2562E7C83A699939911EF210349AE800F26C1820F2FA330C31CD75CAA4DD8E625E4
SSDEEP12288:2LWN6WN/wuR6S970SaLF5jFslumv58EPQKaedfM2X0ox/V14DsGGtFh8qPE8:2LWXMS970S45EB8EIeZM2kox/3Wchh
TLSHT143550A5BAF4C6D27E4EBCF308C76D16A066C2C97A290C91B77AC1D4D7C1B74A074788A
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