Result for 852BAA483873A2FEF447DBB116094923C12C5A7E

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libcrypto.so.0
FileSize1198124
MD59EA3538F5E145E9A4BABE57F21566137
SHA-1852BAA483873A2FEF447DBB116094923C12C5A7E
SHA-256546C41B3786BA1F52EAC38501C0316F25ED2294A02A62CC92557EEA09FB56C12
SSDEEP24576:PcCMjf8L2rUUb3KShRn2Zd2DNIc6On4hSVe6gDA7Q:ECa8irUU1Rh6hSVexDA
TLSHT19F454B4BF787CDF1F6F34574070A937A6924040AA163F5B2EB8DAB5538373452E1A2E8
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
FileSize539980
MD57892561681F29746B8D8CD890421A5E5
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~18.04
SHA-14E1747FA142D26A3C7A2006F896C43133A451982
SHA-2568BE27477153FD4D2B807C41CA211F4F13526C0DDBA86E012144CAB233B31DA2C