Result for CF84F1696AA4452CA7317B153658554DF19615A0

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/android/libcrypto.so.0
FileSize1690848
MD528AD10D0821002CDED5EDF5DE1ACD374
SHA-1CF84F1696AA4452CA7317B153658554DF19615A0
SHA-25610C66A74B29DA4CE3F7C10DDF8A6A6206B2AF54105AA88FB500F195F93D2E05A
SSDEEP24576:m1tpnJcq9WC3eezRRUgw0oCRiW3BEKDcJh6QG6:6tpSq9WC3eyRqCRiWuKDcJh6j6
TLSHT1C5754B17F4E364BDC9AAC830C36F903EA53C76885112697F3289A6702ED69546F1DEF0
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
FileSize680296
MD52E42E97E99148ABAFFEB347CC2B4F4EC
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-1455DDA5110F27E04EA2410A261C0980E838BB64E
SHA-25600F10F9C1788EFDB66911FBFD7637C83CA2A67BBD66B521C42564B5F069501AB