Result for B1BF645F34F68D332E890712F7DA4EF46A9BEF4A

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/android/libssl.so.0
FileSize374172
MD52B3F3E56F11948CD310016AE7EFFADF8
SHA-1B1BF645F34F68D332E890712F7DA4EF46A9BEF4A
SHA-25614475C7B346143D1ED231C30EF3C1763E545FF03F26260E8FC21278827B67438
SSDEEP6144:ueLt/cxFcaYJPMD1XpdJgWqYOWjveyQi1IVcgEoIGBaDglmTlVYKpOTvaMaVIN9t:3t/EYiLdJgWq5DDHcToIqKg0TTOTvaM/
TLSHT14B843B03ED03C8B7E79701B441ABD73BC52C490B452BD787AFC5EE169861765AB0E2B8
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
FileSize588888
MD5853CE1FB3DBF4689FE1D65E749173BE6
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-3
SHA-17D96C65F406D13AC3AEF4CAFB9E5AEC8F5391A9E
SHA-256502483D4DB6ABD4C399B4FDE021BCF057B49D8B48A8AA4C2C244B0087EABAF43