Result for 2BFBACE6247EF6CC4A573847DEF0750EBBE6B5D9

Query result

Key Value
FileName./usr/bin/bssl-tool
FileSize145492
MD5024CF147546D6028A4F6B2006B1A4CFF
SHA-12BFBACE6247EF6CC4A573847DEF0750EBBE6B5D9
SHA-256E6C656286B82467A1D3BCEE620F1DF81B94136C225E80D061C1B7BC23FDFD2A1
SSDEEP3072:tY/Jn5e7o8DtIboxKjLoVCQ4cQ6JjvyxY:tm549DtIboxKgVChcQqO
TLSHT1CCE3075F7553DE12C4F82A7AB12A8590774743B8C3EE22139E64DD2039DE68F193EB81
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
FileSize66872
MD584433285B9D1AF5E501D486E4C515AE5
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-1F771EA84E433FD3B3D8B65B113D73404D675C05A
SHA-256FBA5364F56410A1239B70186B5D4B88720079FA96979BA2F76982E6C64FBF322