Result for FAFD60CF5A10E5B8209292A423638B7CAA22C9DC

Query result

Key Value
FileName./usr/bin/bssl-tool
FileSize144900
MD5179058DE8F6E046BF07566A9DCA11E9E
SHA-1FAFD60CF5A10E5B8209292A423638B7CAA22C9DC
SHA-2564747D6703F53CF94464B36792DDBEF184CD6B0F88C31F068291B074BE03241D6
SSDEEP3072:le0IrpYlhXhjjU8Xh9JpY6kLD9sx4EKSY/dC3:7I2XjjU8hO6usKUOM
TLSHT167E3085AB4538E52C4D82676F26BC754334316B8D3DBA307E828C6241ADF5DECE39B81
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
FileSize65176
MD557E50E656D86B9BB77C8D72B747788B4
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-1221E119930399689E35B712FF11054EEA6C9200E
SHA-256D656675E518221CEC323726037EFF8D575000977FEC676711829ADA714203792