Result for 1FC80A44FF531DE94CA1A0F24FCB9D0B564AB753

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/android/libcrypto.so.0
FileSize1161444
MD59352F08248CA42F5E81C03468FB4656F
SHA-11FC80A44FF531DE94CA1A0F24FCB9D0B564AB753
SHA-256A74E7AC37D37B60A79C83DC695F6034994E7F5C636F5048F44E6FF350043715D
SSDEEP12288:M/t8Wazh6VVYyRI898txdHFeBFt4OT2WHaJTNzNYGlaBvyI3ChnNXFxsXmN37W4a:+t8WKhpyqUHUNz2GwMVpbpVlvKb
TLSHT1FE351A6BF841DD52C9D41176B55EC9C8338783B8C2E57523AE19CA342BCF9CE0E39299
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
FileSize532248
MD5113B8A9CBD5B7285BE92DF949C0B8BAD
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.0.0+r24-2
SHA-1EE17082A63BB95D0E75D892CD21B96E5B36AAA09
SHA-256D2A9B3070A964545CC711DC47FC13BCC0E18616EC8F5D90E8BC52C7AA319CCBF