Result for 825E14A0FA5302C82B1E856B6C23E90A828ECC17

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libssl.so.0
FileSize379008
MD5AD10FA035DC1BFC1B6268066C36BAB78
SHA-1825E14A0FA5302C82B1E856B6C23E90A828ECC17
SHA-2560EC4ED2E21C9AE51A7995012BA6BD5AA50779C5544A689C314EB494BC286B91C
SSDEEP6144:vqFcaYJPQYoYsvq2+HET1NdirtJ021Wjrawp++IqgQhSeXWccd9G:8YqPNd0J021WjrfpXIJQZXWccd
TLSHT116845C12F50D156BD9C2F47C89774580F22932AE6364C2873627D91FFE4A3D9AE387A0
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
FileSize543556
MD5F695439A326C00F2DCBD8B535216B6E7
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-3
SHA-18AD8CFE2A257E6A1023027233676B7109B51CE77
SHA-2562429F9B185A7DED92310B0166C9C9CBC8A86DDD6083C7DBC03F81E21A99DB0C2