Result for A342DC55C225461DAB319B37F02CCF49B66CF372

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/android/libcrypto.so.0
FileSize1699296
MD5159CAFDFCFE84380DF669478044AC26D
SHA-1A342DC55C225461DAB319B37F02CCF49B66CF372
SHA-2568524825D1B4488B2C2F98A766A180C8BFB093734489B1ECF8AF4FA3ADFB8CCDE
SSDEEP24576:RfX0KjighPyON9L2w6Vl7Hl7f1CPzNIA:RfX0QighPyON9L2w0Dl7feIA
TLSHT152754D07F4E3647DCDAAC830C26F903EA534749853126DBF1689A6703E96A646F0DBF1
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
FileSize676048
MD5AD7F905C12E368D4D613BD67AD375483
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-1C49591E8FD10A27EDA4343F28B2490CB111C6E25
SHA-256529FDCB974F401EDB4244967FC3909F84B6562AB01D7D2D81A2CADD2C5B67B4D