Result for A4C6D95483D809C1B1E83F4A33BE5E3F51509689

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libssl.so.0
FileSize362032
MD56ED68F4AB20DB14DD2C58181AE99CC80
SHA-1A4C6D95483D809C1B1E83F4A33BE5E3F51509689
SHA-256F8EACE2CB380BA6FDCD9EE3C925738FA504B883735C18B59A8B0C579291CB16B
SSDEEP6144:lR5xP/9IYI1KKisMQBs8YlHnOD6c1NvpbXmsDK9OMoGYbSMf/kPWzpBzmo:T5xeY3Kis3Pz1rKEKInrSZP2C
TLSHT16D743B0BE707DCF2F2B245F007579762593819099263F4B3FACAB66A747220A7E153B1
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
FileSize539980
MD57892561681F29746B8D8CD890421A5E5
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
PackageVersion8.1.0+r23-2~18.04
SHA-14E1747FA142D26A3C7A2006F896C43133A451982
SHA-2568BE27477153FD4D2B807C41CA211F4F13526C0DDBA86E012144CAB233B31DA2C