Result for 34333D38964BCBE82CE6BA54D8BB71E10D444461

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/android/libcrypto.so.0
FileSize1696488
MD5A19F99C60D6E806C1CF50071D162F386
SHA-134333D38964BCBE82CE6BA54D8BB71E10D444461
SHA-256771720DCADBFE222B6B9D9568BC0C1AF44EA72DD35A7DF038F3727257B2FF349
SSDEEP24576:w8giN8hFKa++BAHEuWHNt7YbgfAKyL8A:wpi+hFh9BAHEFT7YU4KyL8
TLSHT17F754C07F4E3647DCDAAC930C36F903EA634748852126DBF1289A6703E96A546F1DBF1
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
FileSize675736
MD518FA3E4D3B9FFC334601C4CCF8A8D8EA
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-17A3BE83C8CE0DEA9397950F0802B1230E3C4D235
SHA-256638B90834022A5DFE46C13778481D1D22B9B54EABEE26A7BDDF83253C14C009B