Result for 3063C5BC36AC99ABD98DB258D5930BD85EEA7E66

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libssl.so.0
FileSize313496
MD53E74FE8ED79A1AD6EC0166BA33F272CE
SHA-13063C5BC36AC99ABD98DB258D5930BD85EEA7E66
SHA-2567431F8262E6E4D550B52DAC4853C7E90A3AC8185D0C3EECE0B9CB6BF06B5DE62
SSDEEP6144:x4M/eYdSBT+jVtCA6zMWs1uNULCOw9Zi9fahTO41A6CK:4Y/Us1EULiafahTG
TLSHT1BA642B1DFC4D7C62E6C6D13D9EAB8360B33B72DCE3728563391A42988B532CD9674584
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
FileSize463672
MD5D93453E3CF14341B67F3D42B91DD448A
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion8.1.0+r23-2
SHA-150F32966A6D74EF04B858DD43DB380D8C5F4F1D2
SHA-2563A1AB5960890840844767E9E0FC49DFCE23E075665F1F66482EFCF3FAA4F2A74