Result for DFFAAD8354FC09C7F68308621DEC06307F6649EC

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libcrypto.so.0
FileSize1140708
MD5B5A1BF7CC44B92AB17287C596C4DEB68
SHA-1DFFAAD8354FC09C7F68308621DEC06307F6649EC
SHA-256145FA04A19A51CED899236F961DA6C3F1749D036C22C69FE78909744292B80B0
SSDEEP12288:AHH4PViykwJrGZbcySdlMtyZVRgN/0amv3tuyV0C0DEAyxcRPqi828Av+0ai0QUl:AHH4SZs6p0fv3symCcVx8A8uvK2Zhrc
TLSHT13E35076BF8829962C4D4A175B65EC6C8330B13B683D935069D1DC6307B8FACE0E3E6D5
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