Result for 412351100ED9C267142E056D9C774461CE3408CE

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/android/libssl.so.0
FileSize407712
MD566A0C61F3CBA8C8F2B423F2F0DAA0294
SHA-1412351100ED9C267142E056D9C774461CE3408CE
SHA-256227BF10EDD9E9581494FB2ABCADE544FBB51D9E622FF22B0584E3EFB51CAACF3
SSDEEP6144:RbdBFQgY0a1glUMHb56EsBRBC3nfEZAk//zL1Vy7/R2U:DYs5b5IBnC3uB/31Vyl2U
TLSHT10C845C1AF80D7D92E6D7D13C9E4E83A1B22B31DCE33245A335558288CB932CDDA7D958
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
FileSize530600
MD50CF905BBD9B89C26C10CB75620DCD432
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
PackageVersion10.0.0+r36-2~exp1
SHA-1507BBA89E4506282D039E5528C18CA3186A3E982
SHA-25671FD2EE18C226F38A1D41D28E01AEF73DA8179FF04A87D388D4B91F716FE8698