Result for B4F10CBFAA1DC08FB06F80964D80AE93379A92C9

Query result

Key Value
FileName./usr/lib/powerpc64le-linux-gnu/android/libssl.so.0
FileSize526496
MD516F0C359275917CFFAC811CE96DFD93B
SHA-1B4F10CBFAA1DC08FB06F80964D80AE93379A92C9
SHA-256F54E2BD122D786A6FA523EB72C4C29B3A3A4D2FA6E130ED9EBB92BEDDA89C8DE
SSDEEP6144:rDKFQgY0a3Hpk2iZIinoFtB1XQZScbE+oZhPh610lc9tqMYa2ZbZp:rCYdpbiZzkX8NE+66ya2ZbZ
TLSHT15AB4D927320CBB52CB426C3F839EB551735A798506698D537A01430FEEBE7198B1BE8D
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
FileSize622412
MD5FEAFE486A33F22106092ED2628814385
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-1
SHA-15EC80D63FE9B3B13F0ED81B061CCAF0F9D348125
SHA-25673D77D891B832FEF132BAE6D4108CA29B411D22FA94AC8A1E0E54ACA2858E024