Result for 26E9B6F162F275F2748D557058CEF87B42551B21

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libcrypto.so.0
FileSize1360944
MD5F5DE49C52D45D385CC5CB2BB14E4D706
SHA-126E9B6F162F275F2748D557058CEF87B42551B21
SHA-2568E4433B5163A2202F410108B1BA532C6243B22A33AD6931979695BC44C85B51F
SSDEEP24576:OEstFjAhuK0+EMn7WVDGsJIzgijrxlsubzMF:LsDAhu/hM6VD1IzgifVb
TLSHT101559E0BFD0C9A26EEC5F17C88C617E2F62632991A18D15A2D17810DFD8B7E9A7443F1
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
FileSize538924
MD5C5D6BE619A684A93C2A0708E684591E1
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-1CEB4BDED368E7ABADC9F8193748205E1C79AF748
SHA-25642BA7FAA60293F4E89DF82FAED1E57C2B323E0C010DEEEB0B7E45DDA56C9529D