Result for C55326E3E5D224A5F195D8649F4588D72675094D

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libssl.so.0
FileSize340936
MD5D28FBD723C87D90A675CE51D7CD7F54F
SHA-1C55326E3E5D224A5F195D8649F4588D72675094D
SHA-2566AD7387E222440EF987A1FD99231D55CA752A879DFE2D3C71253FB4681A4D069
SSDEEP6144:d6tFhaYUPrGTR4ZFDP2gE4a5VWeq3a8zVSmtcZGtJ39ZWvB2Q9QHUlugybPV:dBYOpFDOR4a5VeV2GtV982Q9QHUl90
TLSHT19F74C637F9029A22C4D4957AB56BC2CC330703B8C2EA75579E49CE341ADFACE4D39295
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
FileSize532248
MD5113B8A9CBD5B7285BE92DF949C0B8BAD
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-1EE17082A63BB95D0E75D892CD21B96E5B36AAA09
SHA-256D2A9B3070A964545CC711DC47FC13BCC0E18616EC8F5D90E8BC52C7AA319CCBF