Result for A218DCF6BDCA1FACB8D7598B662F9040EF96EAA4

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libcrypto.so.0
FileSize1206316
MD5033F4703648FE24EEA23C4CE0D537405
SHA-1A218DCF6BDCA1FACB8D7598B662F9040EF96EAA4
SHA-256AB96BBF2007420F3FD901AB0E73EFA2732B99E51DBA6244F41DEFBC57E9DC444
SSDEEP24576:/cDoVdYhXQL3XexL4kSDmX3bR8h6FIe0oX4z:UDoTeSjrh6FB0oQ
TLSHT17B454B4AFB9789F6F7F245B0070AD3762524400AA163F6B3EE4E275178773416E1E2E8
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
FileSize540264
MD5BCB2833DA2FB636487406208E3D07D1F
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-165484C6ACD76166DD07E89ABA31C10FA2CACB708
SHA-256D9DBEAD0C2402A5F19DED8E915A62D28C115AED423882A03AEADB70D9B80CCBF