Result for 5802FE82AB6BD7755CA27489167968FCBF5812EE

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libcrypto.so.0
FileSize1231700
MD5E4EB93E7396F35EF77989381197CB4E9
SHA-15802FE82AB6BD7755CA27489167968FCBF5812EE
SHA-25607CD7A27828A23DB5D24C08EAF08547F3C50A7274747D0557013F47FD62F8EA3
SSDEEP24576:l/MKTMwhyrw7DymZ2oMX9uP6Z03rNkRaV3VvqvkNrucYBX:l/MGMwh64OUruZ
TLSHT1E2456C03EA4285B5EADB04B4119FA63FD63D45216660DA87FB4CD9349CA3392CB1D3EC
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
FileSize589904
MD55B1287381596E88A1F2076717636505B
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-5
SHA-12CFB6D89708A5370EE4F3EF4D69C7ED8AB73B4F7
SHA-256DE593B141E80816DF357B842A8841F82D73148AC86A434399ADC49B3D60FDEBE