Result for F1FA2765A197CDB419A1E2B3323A68C7487976BE

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libcrypto.so.0
FileSize1260496
MD522707E314B5E60309072C607EAF7D971
SHA-1F1FA2765A197CDB419A1E2B3323A68C7487976BE
SHA-256DB64A1D683D00507F180CC0F06E8B64B99A217E6177092E15A6F258D0DC90385
SSDEEP12288:fLJWqXcsIh/Aq0aoqFVson30N4Q2r188yz3z/MchMf360hglQ4Ez5:fLJWqZjvN4Q2Bez3z/Mchl0hf
TLSHT160454B5EFC0D7C52DBD7E3B89A468BE2A2132190D2D3D8733D66D258BA871D8F6B0450
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
FileSize530600
MD50CF905BBD9B89C26C10CB75620DCD432
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-1507BBA89E4506282D039E5528C18CA3186A3E982
SHA-25671FD2EE18C226F38A1D41D28E01AEF73DA8179FF04A87D388D4B91F716FE8698