Result for AC17B8811BEEE60715EE95A7CC584D88D2FC6BA1

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libssl.so.0
FileSize366264
MD5F04EA55240E37D976F1C87B0688A194A
SHA-1AC17B8811BEEE60715EE95A7CC584D88D2FC6BA1
SHA-256CBB3EDA0C449E99EED210CCBB195578EEAE5D7BF56437F376C0EF74802ED6436
SSDEEP6144:LQaFhaY4Pp9O5QNWQ1ltV3N25W9CWht4APs1nNL0048zP98sSM519:qYA45QcsvI5W9CWYAPsjL0048x85Mp
TLSHT199742B03E91281B7DB8605B041AFE73AA93D813B4725DAC7FB85ED359C21255EB0D2BC
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
FileSize589904
MD55B1287381596E88A1F2076717636505B
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-12CFB6D89708A5370EE4F3EF4D69C7ED8AB73B4F7
SHA-256DE593B141E80816DF357B842A8841F82D73148AC86A434399ADC49B3D60FDEBE