Result for 461703D0F91AB0B5F397559A2742B03CE6610819

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libssl.so.0
FileSize255516
MD526596016C023DCE99FD2237CACB602CF
SHA-1461703D0F91AB0B5F397559A2742B03CE6610819
SHA-2569E2BB00F21981D7977BAFA1C48551A2CCF1D1293756B17EE29115962A6318C65
SSDEEP6144:+EAFlEFQgY0aYPyu96yvpxAmQqxhAZfoEqGVBzn3F1m2awd:3YWqdyvHAm0ZA8n3K2j
TLSHT13A44AEC7700F188BC4C689FBBA738AC28069E1C4A7D58F03375855353E7A9AC593E6E4
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
FileSize494412
MD5853680B70DCA8FB274832FFC27B2B757
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
PackageVersion10.0.0+r36-1
SHA-180B460AB97872A73D5322E92C1DFCB9E6D7042DE
SHA-2565FB95ACF74CA7DDADD585F4DEF102559D608818F18CB32CA2262DCECCE936117