Result for 4921D85D729C743A52D46275E721A0E1DF9D859F

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/android/libssl.so.0
FileSize424128
MD5F8B06238C47B545AAF3A75FE5F760D12
SHA-14921D85D729C743A52D46275E721A0E1DF9D859F
SHA-256E3A760BCF2B277E18B2753B39B6A04F972D7F52103107F15145C3DA95BE8D534
SSDEEP6144:oLhFcaYJPTsWDvsLWG1/tNC7loTDtBnimqAgxspe4dNvkHn6:yY5sW7sLZ2oT7AH
TLSHT1FF94FB57B4E7187DCC95CC31C22BD522A67474C8932AAABF37C8EA302E52B185F1D6D4
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
FileSize680296
MD52E42E97E99148ABAFFEB347CC2B4F4EC
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-1455DDA5110F27E04EA2410A261C0980E838BB64E
SHA-25600F10F9C1788EFDB66911FBFD7637C83CA2A67BBD66B521C42564B5F069501AB