Result for BC0FAF46F250FB98E6A70ECB49B0559B96815A04

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libssl.so.0
FileSize385776
MD5E465F707BA641B6466360B902D490E8E
SHA-1BC0FAF46F250FB98E6A70ECB49B0559B96815A04
SHA-256D2B3C5E69A1D9474232323B08921C4774DD57293CC38B22D7695E744673A4A01
SSDEEP6144:HyGTFhaYUP38zPWoJw2cKw0YEjGxySB3Eh5d+JZEr7I:HyNY4boJw83jGxySB3EZ+Jars
TLSHT183843C16F81D693BFFC1F0BC856706E1E635B1A96318C2693D278ADFED813E8511A360
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
FileSize546008
MD50D92C17C8CC746365A7387AEB8EA841E
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.0.0+r24-2
SHA-19EA8357BC15276F329800B87B85FE924BB5A69EB
SHA-256B7604D234939ABBD7BF4EECD3F857DFBE018BF62C60C50690FB09ABB762503FC