Result for 4BAC8B48B46A007A01151AC98DEE3B6F66F2C0D8

Query result

Key Value
FileName./usr/bin/bssl-tool
FileSize155856
MD5D33766BF340EB9A956EB8571AD0951E6
SHA-14BAC8B48B46A007A01151AC98DEE3B6F66F2C0D8
SHA-2568B8D1F0A00BD6F7A4ADD6B65F26C7238B9993E9BB4EB17E7886E5E4389C45D02
SSDEEP3072:iel8Yl/CHMppCPGXqtXlYo0ULBovXZFpTU5UbxvRwLAeGhxKZ:/yOajPGXqtXlYo0ULBoHpY5UbDwm0
TLSHT1ECE33C0AF50C9D3FCEC271BC658A06B2F137B1641718C1EB6912881EBE076DD1999BBD
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
FileSize65420
MD55E4508BB411C654574FD2F7B49E9DC4D
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-5
SHA-13F0379972C072055543C8112861F39743046C718
SHA-256E0E6DF3D6D6535513E4977BF57FBA39C4C82A7D1238E7F2C965155C94CB25F00