Result for 1A4566E3FAA193A88EAFBF2BB21EBC2D96320781

Query result

Key Value
FileName./usr/bin/bssl-tool
FileSize157776
MD5DDA37D5E0C022FA1C9F6933032BFF567
SHA-11A4566E3FAA193A88EAFBF2BB21EBC2D96320781
SHA-2566284AC681D1997B058876AAAE538788C1269D62D670A3690033AB893E85B69A6
SSDEEP3072:mxsZdCpu9drfZquI/sosgyEW/ngACXlwZGRWZnuCXYwPUtBFQ:mSCSrfZquI/sosgyEW/nbCVwqWZzMm
TLSHT1EEF34A16FA0C1D37CECAF63F15CA0679B622762C5312D4A33521C61AAF0BBDD59792B0
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
FileSize65700
MD5BD854DADA7144A3CFFE06096C1FFB089
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~preview2-3
SHA-13A97D0645DB4D6984A23B34C23B4E721CA2DDE79
SHA-25654A0B7FCF8E8DE72B83FCFA9A86CD569917A1CC90E97FEF1470E94942F0E1E51