Result for 845C9F900484C6E2DF160B8DB402F7734D478B7D

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/android/libssl.so.0
FileSize423648
MD56B6E51DE2D4B964A03A500D3E61545F0
SHA-1845C9F900484C6E2DF160B8DB402F7734D478B7D
SHA-2569657EA27C0C56465C4E9F48EE15982F16341B30A1C12CFE50B7FD7761266B063
SSDEEP6144:XyFhaYUPxKVyJb4hPbZZqdHOZ3oA8W3Kd4Woy7h2iO0fQfpk:zYkKsJ6zZAuZ3omp/m2iO0oR
TLSHT1C294F953B5E61DAECD95CC30C22B9121F63874945226AEBF2794FB302F51B18AF1D2E4
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
FileSize675736
MD518FA3E4D3B9FFC334601C4CCF8A8D8EA
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-17A3BE83C8CE0DEA9397950F0802B1230E3C4D235
SHA-256638B90834022A5DFE46C13778481D1D22B9B54EABEE26A7BDDF83253C14C009B