Result for 454BA46F8BFFB7045CA8368386A1A957E426888C

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libcrypto.so.0
FileSize1350560
MD5CA9527DB5575DDCCA560F514F1C4430E
SHA-1454BA46F8BFFB7045CA8368386A1A957E426888C
SHA-256697222755CD009002C0840952A3FC801792A68D4BB84F915BE90043A133B0532
SSDEEP24576:9E2HywkaF+UsO+c8Qcmn6eij2dOMl1dcph4wT6+:9hHPkaF+g+cTcmn6eijkPoph4wT6+
TLSHT154557C0BE90CE93ADDCAF1BC884747A9B02E729B1610C45A35268D0AFDC76E957747F0
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