Result for B689EDAA4BE4702CCEBBCB4090F63FCB77066F45

Query result

Key Value
FileName./usr/bin/bssl-tool
FileSize157132
MD59472B50F0A9E542928BDF30A298BEAE0
SHA-1B689EDAA4BE4702CCEBBCB4090F63FCB77066F45
SHA-256F5F5198D80B6F392B5E42ACD595241A8AB410301DF283AA300857C4F39E1EA04
SSDEEP3072:dJHcd31W5xuutmMNKKBsfz4Bu+jOl4gbDQqBEUL:dCd31hutzKKBcXlD53L
TLSHT11DE32A42EA53C2B4D5C302B9006FE33BCA346915C35BCA97DBD5DE30D8622665A2B3F5
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
FileSize70980
MD51D031D6AF3EE9FDCF8B63E42BCD669C8
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-111C9257A8D4963D2B611B632DD6CC86BDFAC4594
SHA-256D1C2A2A200A700A6C0BA3CD1627B83A419F60B5659E990ECBDB549DB832347AF