Result for CE318850A8B625E4242056FDBB6FEF2969C05F5C

Query result

Key Value
FileName./usr/share/doc/android-libboringssl/changelog.Debian.gz
FileSize2358
MD561E6D057FACC0C8B81740CAEAF6B990D
SHA-1CE318850A8B625E4242056FDBB6FEF2969C05F5C
SHA-256AFBD906F71883D530ED720203EE45C550F6EF67C052943386548B81ED3162F0A
SSDEEP48:XrQpkhVlkoZs6meF1/WiaMyPLwV5y5rsTuj+Fa7VDnhvzTLBEfipY:bFJsNeF1/WMybr4JFuzvrmff
TLSHT1CC411B2574ACE9D0B564F302D04FCDCD5D93AC003C541A09FFBF320921A1A6A0547557
hashlookup:parent-total5
hashlookup:trust75

Network graph view

Parents (Total: 5)

The searched file hash is included in 5 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize537616
MD56DF33E2989B1C5D3A4B82B6801329638
PackageDescriptionGoogle's internal fork of OpenSSL for the Android SDK 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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion13.0.0+r24-2
SHA-1B45619161F2B8E57C2C2E68BCEB8224EDF34FE07
SHA-256E84CF9E9CCD53DF722A5728EA78F501E2525E59FE1F766327A53AD52C951BF5E
Key Value
FileSize691364
MD5668A49FDB8575A88DBE2167D8DF63101
PackageDescriptionGoogle's internal fork of OpenSSL for the Android SDK 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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion13.0.0+r24-2
SHA-10BD18895E91E3B139E4E5E48D6026150DD751AF4
SHA-25618E6F45AD02B09AD0D529833D8ECA7EF1E664D85FA943AEFE8256930987D6202
Key Value
FileSize532248
MD5113B8A9CBD5B7285BE92DF949C0B8BAD
PackageDescriptionGoogle's internal fork of OpenSSL for the Android SDK 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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion13.0.0+r24-2
SHA-1EE17082A63BB95D0E75D892CD21B96E5B36AAA09
SHA-256D2A9B3070A964545CC711DC47FC13BCC0E18616EC8F5D90E8BC52C7AA319CCBF
Key Value
FileSize675736
MD518FA3E4D3B9FFC334601C4CCF8A8D8EA
PackageDescriptionGoogle's internal fork of OpenSSL for the Android SDK 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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion13.0.0+r24-2
SHA-17A3BE83C8CE0DEA9397950F0802B1230E3C4D235
SHA-256638B90834022A5DFE46C13778481D1D22B9B54EABEE26A7BDDF83253C14C009B
Key Value
FileSize546008
MD50D92C17C8CC746365A7387AEB8EA841E
PackageDescriptionGoogle's internal fork of OpenSSL for the Android SDK 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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion13.0.0+r24-2
SHA-19EA8357BC15276F329800B87B85FE924BB5A69EB
SHA-256B7604D234939ABBD7BF4EECD3F857DFBE018BF62C60C50690FB09ABB762503FC