Result for 5E63C1EE788CD3A6B61BF7285EECAA7B770FA5BF

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/android/libssl.so.0
FileSize344636
MD50F722E7197285B09AE136D35AEEAE9B2
SHA-15E63C1EE788CD3A6B61BF7285EECAA7B770FA5BF
SHA-2568D465001DA9A42F3F926C9C3BADB5A17D7D33693C69ADAF1B805EECB497B8E02
SSDEEP6144:xX9FhaY4P+1uecPzr9pJCgHwtuHXWlsWS/eLTSApuoHtlAcI+2OTbP:xEYpH4ppJCe56CApdtlPjTr
TLSHT11774C877F8438A22D4D0257AB96BC1C4330B0778D2EA76179C1ADE346BDEADD4D39281
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
FileSize535720
MD5BF17346E9072D1A79C6480F58C470CCC
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~preview2-5
SHA-1236240BBEDDA7B6CC599DEA4753EFF3B5B26E266
SHA-2567E1B04C861C0F023561A92D1FCB9A6DC01D4436E3D5968AEE9CACF8F9038EC23