Result for D9D428782CB917DB69B77C1DC97639F83EDD2EC9

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libssl.so.0
FileSize381752
MD50E48A172F57E1FFB7CAD43583215B626
SHA-1D9D428782CB917DB69B77C1DC97639F83EDD2EC9
SHA-25631D8ED5E02C879EB8B9D6B5EBB46C51B409B5E1E371610F3E68152DC588EE259
SSDEEP6144:OtFhaY4P4lU7L3BqQzXPMIdyRFCI9a9u2UNcrIN:TYpUPBq0PMIdyRM4a9u2Uu0
TLSHT1AA843A02F90D5A2BDEC2F5FC856706E1F52472D96318C16B3A13895EED8A3DC760A3B4
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
FileSize538924
MD5C5D6BE619A684A93C2A0708E684591E1
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-1CEB4BDED368E7ABADC9F8193748205E1C79AF748
SHA-25642BA7FAA60293F4E89DF82FAED1E57C2B323E0C010DEEEB0B7E45DDA56C9529D