Result for F9753E7F26621444F5A292AC0FD1B4479F32E89B

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libcrypto.so.0
FileSize1382872
MD596075FAE07EE4201EC88E4C52C0F22E2
SHA-1F9753E7F26621444F5A292AC0FD1B4479F32E89B
SHA-256890A16DFD9A4B632BCB54F13A69B569C38FE3AC00551C377C084F1E135779268
SSDEEP24576:XFWuKFhITrXdMad8O42jZtgxYncpZP7MP:XouchIThMk8pmgxYncz
TLSHT105558D0AEC1DD92AFFC5F13C84862792F236B0986F1CE1543A2A821EFDC36D956453B5
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