Result for 28E32E3D55FF65CE3FCB0C2B16632F83988253E8

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libssl.so.0
FileSize337428
MD58F34E9179ADF1DA035A84B2B69DFBAA7
SHA-128E32E3D55FF65CE3FCB0C2B16632F83988253E8
SHA-25625CC4F7BD25CDB40521C8AD2F3F2AD21CC6510F6199B3355BC79A31675FFE228
SSDEEP6144:OBliFQgY0aGqHOfDSucbMaVp1stSh56BKWUvqTO6xx7zUBM3kBxM0:xYYqwSuC3sSP6BKWUvqTrBk8
TLSHT15C74F937F481DAE3C6C05779775EC3E8332757B0C3CAB212D81896346BBA49E457A682
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
FileSize483776
MD55094C0EFEFC2C735F548CACBEDF44C69
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-1
SHA-124C9E99AA2B4130C90A04D859340943B59E124B0
SHA-256283B00D520F9B058AB48EEEEA5176B13ABFDB85FCC81C7D92DB7F044EB074E81