Result for 1346F1C07B6ED450292F7C97E33F1EDFB1D65E20

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libssl.so.0
FileSize349508
MD5C0B394DEB57C527A454C66CF381689E2
SHA-11346F1C07B6ED450292F7C97E33F1EDFB1D65E20
SHA-256E492C252C869BAE77F54E67ED1EB131D84D5B8DAE973179AF8EBA05153036353
SSDEEP6144:g2lFhaYUPirdRc4Fq1D/sbLqlVyQxowJH1QexEuuG2AnS18UZCaeEP/:gtYRVq1DkPqTyQiwdlRlnS18UZC/Y
TLSHT14C74B737F8429A22C4E41976B96BD1C4334B0778C2EA76139D09DE346BDFADE0D39285
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