Result for 1428629E2529C30E10E49AFA3DDD892C07516A4E

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libssl.so.0
FileSize313496
MD5846D1B023DC21C16C3C0CFAB3615CBB2
SHA-11428629E2529C30E10E49AFA3DDD892C07516A4E
SHA-256E0F761F940219BFE8721A239A6C3A5BB94A55ED7ADD35663EE9047D719E07329
SSDEEP6144:2M/eYZxnJH0Msc1sufUfShYIsyFLwWJeJK6Cr:0YDoc1XUfSrFwWJJ
TLSHT12D642B19FD0D7C92E6C2D23D8EAB8351B32772ECE3728563361D869C8B922CDD674584
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
FileSize467472
MD5FA5B5736F7912193F2DD41AED9B3ABDC
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
PackageVersion8.1.0+r23-2
SHA-11A4E7E5ABE2737557FF84F481B94B0D236AE3DC4
SHA-256F292CAABFE11C95AEF2E53D08A98B406E79815348F8203AFE28C33EB01D711E0