Result for 82494BA5EE28ECA85EB87C68E05C7910DFD1F763

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libssl.so.0
FileSize370224
MD52CBB65B94FEDADE007050233DECDD74D
SHA-182494BA5EE28ECA85EB87C68E05C7910DFD1F763
SHA-256FBFE591A74EDDFC0A12623F21A2F9AF0BE2B0FE0765A85DEDC60EEDF5B755453
SSDEEP6144:j/MMSIYXL192tkObz1ZxWN5wwM/vsgHwXbuwH07/Z:ZYXxo1ZyewM30XbuwwR
TLSHT13B74290AE757DCB2F2B244F0075793A25938690A9273F5B3BECA76123471349BE193B4
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
FileSize545608
MD5DC0FA3DE6781E292D08780C161813353
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
PackageVersion8.1.0+r23-2
SHA-120AF0662B6A1D99C19959D05A3744A5389912E52
SHA-256E9616C11931F58605FA709AC0843EA3FD9D54F84CB0200ED17F1F92649B0DBDC