Result for 72F982409DA0CA06347798196DA09E4D1D521CB4

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libcrypto.so.0
FileSize1184456
MD5DBA0FA74563D52F794223D5C233E9E6B
SHA-172F982409DA0CA06347798196DA09E4D1D521CB4
SHA-2568FA66D90A16848C22EDC996D4D3BBFC01D13BD71E47C1006E3D6165A24EDA123
SSDEEP24576:mOmJBWbwhXYN2u92rOKBmyH4PYoN1kvKm:mOm6whXnPBNO
TLSHT198452A37F8429D52CAE41072B55FC9C03347537892EAB6229D2DCA342BDFACD0E39695
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
FileSize535720
MD5BF17346E9072D1A79C6480F58C470CCC
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-1236240BBEDDA7B6CC599DEA4753EFF3B5B26E266
SHA-2567E1B04C861C0F023561A92D1FCB9A6DC01D4436E3D5968AEE9CACF8F9038EC23