Result for BF5412983FD35B48A116636E042BB4F5CF0C1324

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libssl.so.0
FileSize194076
MD5A220548AEB6C86E48C720994A2F059FA
SHA-1BF5412983FD35B48A116636E042BB4F5CF0C1324
SHA-256903C637153828FF696B26335CAF4D7A429FF1AC247201A74FB1F3E7921777584
SSDEEP3072:Hb2A8VBIYBq+bfjVaU6dJRz8b8QXGwN1vt+sGRQiAan2OaIjapYdXAyc2pE:v8VBIY0+bfjQxz8b8QXlPv8n2VzGe
TLSHT17114AE03B45F1D47C0C24D38A4A34ED3C21BA145A3A5DF27F49CA4762EB69EC4AED6E1
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
FileSize420128
MD5ED675CB871B6287A74DF0CCE784CECE3
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion8.1.0+r23-2
SHA-126D561A12666FB43805304531C72A3A040490299
SHA-25621C1D992B260D61A6016732FA0295678BB0F6D44D534D0A1BCE011FBF8FBAC04