Result for 8FE69D5D58FCA7FF1BE6391BBD39278DD0D00A87

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libssl.so.0
FileSize370224
MD5B6AC9487E5B0B45807ED2279106324C7
SHA-18FE69D5D58FCA7FF1BE6391BBD39278DD0D00A87
SHA-25648D95E89A637A5ED3545443082866DD22D9533380D83EFDB3AD7E9B1AB29A054
SSDEEP6144:n/GCMSIYlX1Rk0udK/KKu52C6NztgoXVAHu6gC/a:/aYNMw/s6NxJAHu6a
TLSHT17C742A0AE717DCB2F2B244F0165793A25938690A9273F5B3BECA36523471349BF193B4
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