Result for D23A86CDD8E039BB65D5F04B47D44A69CF3B6037

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libcrypto.so.0
FileSize673776
MD565E374884CC2DAEF159503BFE9C03AC9
SHA-1D23A86CDD8E039BB65D5F04B47D44A69CF3B6037
SHA-2560F3045F14DD61B2E9FA083FB8448B867519DC9457E07E640DF3294227CA371E1
SSDEEP12288:0cIesqghgeZ1HnoosNEcRAXEyYAnSqA8KRls6blaA/VHY84JH868hhZI:0crsqghgK4XyH8VhH
TLSHT1CDE49C42FDDC1E47C0C6A57B35A30B663231C489A3D5AF07596CA0BA2F1BBDD16683D2
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
FileSize420128
MD5ED675CB871B6287A74DF0CCE784CECE3
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion8.1.0+r23-2
SHA-126D561A12666FB43805304531C72A3A040490299
SHA-25621C1D992B260D61A6016732FA0295678BB0F6D44D534D0A1BCE011FBF8FBAC04