Result for F7A818F640F578E9C9173961F4FCD50D7D9D3B37

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libcrypto.so.0
FileSize1199200
MD5F72C93970341A15AC54D580658D1588F
SHA-1F7A818F640F578E9C9173961F4FCD50D7D9D3B37
SHA-2569C03441289E71C833A12B7D95B5669FEE69610314DC8C0B27B4F8504505EFE6A
SSDEEP12288:lo+8W4jhD04/h6VVIdxQBBD5GTvoveBz+v9pt4qLIYl5c8MFr1E84Qoc2IYoNNr7:b8W4FD04/hpvQBdpnm0mNrAtkrvKI
TLSHT1BB45182BF8419E42C9E4117AF55FD5C4338747BCD2EAB2129D0DCA342B9F98E0E39295
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
FileSize537616
MD56DF33E2989B1C5D3A4B82B6801329638
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.0.0+r24-2
SHA-1B45619161F2B8E57C2C2E68BCEB8224EDF34FE07
SHA-256E84CF9E9CCD53DF722A5728EA78F501E2525E59FE1F766327A53AD52C951BF5E