Result for 0F27EB74E750B12F2F6C0D12C8304E91DEFC0D0A

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libcrypto.so.0
FileSize1181664
MD53F83DDBEC6AA857167364C25D0B7C1E9
SHA-10F27EB74E750B12F2F6C0D12C8304E91DEFC0D0A
SHA-2565AA3A43DC587DB395CFFC70B2C9E9AC680EC3A561FBA686EBED102C136686A06
SSDEEP12288:CxAIl+H473NqmnYiHh9AqtIHFqZUmpofu+CFgKdHwP781pUmLOyT2/ghUP1IWVsV:MAjH4LnxPo8Vumvhm1IjYZvK/Zh7W
TLSHT18345186BF8929A62C4D06171B65FD6C4330B077982DA7606DC1EC7303B9FB9E0E2D685
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
FileSize532864
MD5006583C4375BED068B9EC71FB59D35E3
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-19FFBEC3661595D5DB74BE253680D12F010E914C9
SHA-256F6600FCD27D8E8D44AE772D7CA691F706BA84DB50B0CEF23DE9A55BF3F41E499