Result for 584A3D20F4AF625B13F8AD5F66E14A22CCD15C85

Query result

Key Value
FileName./usr/lib/powerpc64le-linux-gnu/android/libssl.so.0
FileSize526496
MD506C717ED87987CA2AD32832574D546EF
SHA-1584A3D20F4AF625B13F8AD5F66E14A22CCD15C85
SHA-256461355B98DD481A1D7E0C283EB9A1254E8B045266A25018AA1A3EE6CC55EA67B
SSDEEP6144:ODKFQgY0a3Hpk2iZIinoFtB1XQZScbE+oZhPh610lc9tqMYa2ZbZp:OCYdpbiZzkX8NE+66ya2ZbZ
TLSHT198B4D927320CBB52CB426C3F839EB551735A798506698D537A01430FEEBE7198B1BE8D
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
FileSize622784
MD5DFB58ED1825B3956C82E6101199DAE64
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
PackageVersion10.0.0+r36-2~exp1
SHA-1305CE20E475ED8D01D14E2946836697D4E1E5197
SHA-25609C90EBF1706608F9D87C1F49873248B506910AD9EADF7A9749AD74E56B32EC5