Result for BB479D19D91FE7E14397823F1BDF08971ECCC632

Query result

Key Value
FileName./usr/bin/bssl-tool
FileSize145476
MD5F2385BF51149F788B6978BCD5C456744
SHA-1BB479D19D91FE7E14397823F1BDF08971ECCC632
SHA-256AF82B2555F2B2D2DD71DDE071BA7E098F73FD9BECFFEC90C94CA7B4A7B37A474
SSDEEP3072:ehMJlHyvSDD+jfAPTaPzYUOlM9I11A5yBq6:e053D+jfAPTOvGM9d4
TLSHT1FBE3199E7563DE12C4F41ABBB12F8590374743B8C2EE22139E64D9302ADE68F1D3D691
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
FileSize67628
MD5AF916158E6E7842A6665ECCFC7B96DA6
PackageDescriptionGoogle's internal fork of OpenSSL for the Android SDK - tool 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. . This package contains the boringssl command line tool.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-boringssl
PackageSectionutils
PackageVersion13.0.0+r24-2
SHA-155E7AA2681E1E9ADF09E7C12FAAD3AF3FE9D4126
SHA-2560158A00589DEA5497FAC30ADB179D326C4433FED4F09645E8313774C6C13998E