Result for 05A89890A6D20B50D9375FA3302A465064D46AD4

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libssl.so.0
FileSize333332
MD5208E390575D3256CA2F287603F6FFBB1
SHA-105A89890A6D20B50D9375FA3302A465064D46AD4
SHA-256F2C03A18A29C779217C382D79A1EFCCB33D9CAAF3581015B1DC425F230A3BD7B
SSDEEP6144:dP6OhmLgFcaYJPo+J9i+m5lj3fd7Zbq0brLtDXSOMF+yHmIjfEDRqmMr4hxQJJ6o:dbmmYNfir/j17h5tDZWyNqNr4zNFk+jq
TLSHT1DD649377F8028DA6C4D06675BB5EC3C4330B03BAC3E9B516995986346E8FACE4D39781
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
FileSize527092
MD5669C3C9093C596394C66215F0B23D8AD
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-1C5A191874558B0D734AF2BD56D67A8A2A89A3148
SHA-25609F0209B48E9A35E071A86E9794460E33403199864668047A13D9C9C3A4272B2