Result for 3442E34A9994CA27D0898B485349CD2EC42055A0

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libcrypto.so.0
FileSize1598704
MD5747BD1911C751C9801390AF57E673BCB
SHA-13442E34A9994CA27D0898B485349CD2EC42055A0
SHA-25662ED71A06D6EBC842EA44B660546A53C65C4A6CB290AA6E7DF1AE9A797AFF0E5
SSDEEP24576:JcmN0hTad6Jm+Yf+SHGQNaBJgzlFXicZX9LB8xp/t+6Smv9gQzKGR:CmGhTLZ9u
TLSHT150755B42E3AE4DB6F96A48F0435B7536FD39003D11B3B4CAEF4EE76018621A1DF59289
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
FileSize691364
MD5668A49FDB8575A88DBE2167D8DF63101
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-10BD18895E91E3B139E4E5E48D6026150DD751AF4
SHA-25618E6F45AD02B09AD0D529833D8ECA7EF1E664D85FA943AEFE8256930987D6202