Result for E50DF67D63B59695936AB02132D4ED2D207B0158

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libssl.so.0
FileSize255508
MD5D3B2AEC9E0CCAE9CB27390979D143BC4
SHA-1E50DF67D63B59695936AB02132D4ED2D207B0158
SHA-2565567E395DED6EDEAF8C90D94D7805B2D14FC6B5C24D5150AAD92CEB64E702F07
SSDEEP6144:2o1VBIYz75qX7TaNxv7gou8PBtNmPSTlnAGaabNryrNeGe:aYvQaNx8L8PPNmKptaabtk
TLSHT148441867F8469BE2C1C11BB8F75AD39533375774C3CA7A03D90946342BB28EE492A5C2
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
FileSize416668
MD5098E63CD65F25858AE726E6DCFC33117
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
PackageVersion8.1.0+r23-2
SHA-16BD8D1ADB16243C5E29750A21339E0A6DBBB3ED9
SHA-256C59AA944A81565F3FA04CB3E0D29E959A4271C04E88F59BC207C42BACCB12A4C