Result for AEBAD9BB602EFA44F796D1758AE24D00E3549D92

Query result

Key Value
FileNamesnap-hashlookup-import/usr/share/doc/android-libboringssl/README.Debian
FileSize986
MD52F4C597D00D2256BFCF1DF18874BE4B1
SHA-1AEBAD9BB602EFA44F796D1758AE24D00E3549D92
SHA-256A28F69ABBB46273CABE34F20F652CD3FDAB2AD7FB132086298566EA535D92E69
SHA-5129CC0D2ED5BC60B954AF1CD5B0AF76F95E9BADE40F98F4D21E2D2F7862333E6B85B8E47041FA1563FC1334EA5C1B43C8359068A325330969AC976A1FE9024D6B4
SSDEEP24:fjMu5cfKBXutHZeEyEuerewfyZdAF3fjWJKNbucN:rMacfKBu5JduSyZeFvqUNbuQ
TLSHT154112562B386537117D9F6D9FB149004D78AA139FAF242FA645C81572247818C777C4C
insert-timestamp1728990626.9987605
mimetypetext/plain
sourcesnap:M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_399
hashlookup:parent-total59
hashlookup:trust100

Network graph view

Parents (Total: 59)

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

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
FileSize467472
MD5FA5B5736F7912193F2DD41AED9B3ABDC
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
PackageVersion8.1.0+r23-2
SHA-11A4E7E5ABE2737557FF84F481B94B0D236AE3DC4
SHA-256F292CAABFE11C95AEF2E53D08A98B406E79815348F8203AFE28C33EB01D711E0
Key Value
FileSize545608
MD5DC0FA3DE6781E292D08780C161813353
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
PackageVersion8.1.0+r23-2
SHA-120AF0662B6A1D99C19959D05A3744A5389912E52
SHA-256E9616C11931F58605FA709AC0843EA3FD9D54F84CB0200ED17F1F92649B0DBDC
Key Value
FileSize535720
MD5BF17346E9072D1A79C6480F58C470CCC
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~preview2-5
SHA-1236240BBEDDA7B6CC599DEA4753EFF3B5B26E266
SHA-2567E1B04C861C0F023561A92D1FCB9A6DC01D4436E3D5968AEE9CACF8F9038EC23
Key Value
FileSize483776
MD55094C0EFEFC2C735F548CACBEDF44C69
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
PackageVersion10.0.0+r36-1
SHA-124C9E99AA2B4130C90A04D859340943B59E124B0
SHA-256283B00D520F9B058AB48EEEEA5176B13ABFDB85FCC81C7D92DB7F044EB074E81
Key Value
FileSize494984
MD59443336D1892E8E3924F6F2CCD51CD64
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
PackageVersion10.0.0+r36-2~exp1
SHA-1250A7DBE49E19693F59F10A87B08F9BACC4A1550
SHA-25649A0D874D220F3E4C702BB2BCD322CC950FBD9267A80B401E1EDAD5908DC2DDE
Key Value
FileSize420128
MD5ED675CB871B6287A74DF0CCE784CECE3
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameandroid-libboringssl
PackageSectionlibs
PackageVersion8.1.0+r23-2
SHA-126D561A12666FB43805304531C72A3A040490299
SHA-25621C1D992B260D61A6016732FA0295678BB0F6D44D534D0A1BCE011FBF8FBAC04
Key Value
FileSize534748
MD5527978F1D4E59F7A292072C3A02F6AA3
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
PackageVersion8.1.0+r23-2~18.04
SHA-12C7E64AD427B366280FE3BB4F3CC6AB0D30FA729
SHA-2561D1C81CABA2BF12D369AB1C10F473108440306A26487ADB93A1D506263EBF0EA
Key Value
FileSize589904
MD55B1287381596E88A1F2076717636505B
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~preview2-5
SHA-12CFB6D89708A5370EE4F3EF4D69C7ED8AB73B4F7
SHA-256DE593B141E80816DF357B842A8841F82D73148AC86A434399ADC49B3D60FDEBE
Key Value
FileSize622784
MD5DFB58ED1825B3956C82E6101199DAE64
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
PackageVersion10.0.0+r36-2~exp1
SHA-1305CE20E475ED8D01D14E2946836697D4E1E5197
SHA-25609C90EBF1706608F9D87C1F49873248B506910AD9EADF7A9749AD74E56B32EC5