Result for D3699572A928B6E2E6BC2517BE727B1A018B00F8

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libssl.so.0
FileSize345612
MD55459279953029D400AA961E2F688A5A1
SHA-1D3699572A928B6E2E6BC2517BE727B1A018B00F8
SHA-25632F14FD226D48984F4040BE5756E4E3CD4294A854BD1B4AD11627883A50601D9
SSDEEP6144:HY039WgFcaYJPyADwaUPS1a17xdodUsxjG/qIxsPZ3IqRvRk05XcWOSl:HL/YIzl17xdDaPh3IqDkCXOS
TLSHT1B874B577F8438E92D4D026B5BB9BC3C4330B0779C3D9B2169C1AC6346A9FAD94D39681
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