Result for 50733A3016E7FAD6649B264C700EB931D51BF1A2

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libcrypto.so.0
FileSize1145808
MD5FE42ECA7D7B191EEEED521978CB01623
SHA-150733A3016E7FAD6649B264C700EB931D51BF1A2
SHA-256B89A93F7FCA8F595C822F835C30A28AD65CD8FE6C54671AC84490581C596FE8B
SSDEEP12288:QrF36mJwilwh68tjqwAJ3viSuSIrk3gT6iCrLAgW2tuSMZQ0MPgntTkUaJ/3Lnco:fmJvlwhn/oiwYBr2tfiQAUHPpjZL0vK
TLSHT1DA35286BF842DD52C9E05076B55EC9C4338743B882E97513AE19CA342ECFACE0E3D695
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
FileSize529656
MD5E8FCF347C2F5DDB63E76C28A4A047C64
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
PackageVersion13~preview2-5
SHA-1D33B69179C67FFE077BE6B0DC99E7868F43C1088
SHA-25624F8B1D05480A09EFE263A78B791E2F5B54DBE15A42A5F74B0ADBDA9C11CC61F