Result for 982DB884F10EC322205F4992D3B00EF42A37C6B7

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libssl.so.0
FileSize498976
MD598FC420525D1D9046E819BB128A509BF
SHA-1982DB884F10EC322205F4992D3B00EF42A37C6B7
SHA-2567BEBAE234DDC6BB21722873BFB514D725006E5BB14A6E6B930E9CEB022BF99A8
SSDEEP12288:G0YSbfM1M1xnYWZT4G1Y8xHm1kNQ42GrLmU/lD/:Z9nYWp4G1Y8xHWtXGrt/R/
TLSHT12FB42B85E76A8EF2F66205F0426F7331A838443A7172B5C6EF49F7715822250FF9926C
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