Result for DA647B805FB7767A5A3901C93F4CA28FBFD31F42

Query result

Key Value
FileName./usr/lib/powerpc64le-linux-gnu/android/libcrypto.so.0
FileSize1641520
MD53B7AABBAA529486F350C00FBE837948B
SHA-1DA647B805FB7767A5A3901C93F4CA28FBFD31F42
SHA-2564E48C3E6B43697A944A191B1205FBA02ECBAB3F42736B2C52478155B1C47BF0D
SSDEEP12288:8JvWU1OvMHsM/tU9j2CTQv25/pOzmWYgvHV99hRXyYmS2Z2:8JvWXvs1pCTse/pg1hhwhTZ
TLSHT182752B27330CFA67DB42593FC69EAA18338A7809066559637710030F6DFEB15CE6AC6D
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
FileSize622784
MD5DFB58ED1825B3956C82E6101199DAE64
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-1305CE20E475ED8D01D14E2946836697D4E1E5197
SHA-25609C90EBF1706608F9D87C1F49873248B506910AD9EADF7A9749AD74E56B32EC5