| Key | Value |
|---|---|
| FileName | snap-hashlookup-import/usr/share/doc/android-libboringssl/copyright |
| FileSize | 19529 |
| MD5 | 8E983B41C5123BF92122AD0EC6950CD3 |
| SHA-1 | C20523F7F1727E101555CAAA440CCC237E7A30BE |
| SHA-256 | 6A8C4D831B6F6A37D6742505BAADF36A04E99374D7AB545DFA141F2663853F5B |
| SHA-512 | D0042008AEEAAD002815A1F8E2E5365E6C67EC8E5A251471A981078CD87684116D298D6EC338BFF83984099A785BD0BDA8E4CB4982288D0B88800548059D5DC7 |
| SSDEEP | 384:tVwoow8IhUFYSd/+TAOIrs0rsLCIMHM0hAt74rs0rsL+8bwC5JPurscrsfWHj9U:zETwTJIDWtMHX2p4Dn8bwC5c97j9U |
| TLSH | T11792554B9C2EE3A70ED1A6EFBCF5E569A14750C71A06AA4D370CC0E46F8295890E3674 |
| insert-timestamp | 1728990627.033159 |
| mimetype | text/plain |
| source | snap:M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_399 |
| hashlookup:parent-total | 38 |
| hashlookup:trust | 100 |
The searched file hash is included in 38 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| FileSize | 181736 |
| MD5 | 6CE7FE274F88888E4579D39576DCC073 |
| PackageDescription | Google's internal fork of OpenSSL for the Android SDK - devel 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 development files. |
| PackageMaintainer | Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org> |
| PackageName | android-libboringssl-dev |
| PackageSection | libdevel |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 18DDCAB4081B9BA06A7BF95A6EAC2CB3E27F0223 |
| SHA-256 | 87EED1F1549DB594739ABC910FF70CE911FB2FCD298E18FA46678326B2B64E43 |
| Key | Value |
|---|---|
| FileSize | 181380 |
| MD5 | F6A583A383341ACE7F0E5FCA1DEE5941 |
| PackageDescription | Google's internal fork of OpenSSL for the Android SDK - devel 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 development files. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | android-libboringssl-dev |
| PackageSection | libdevel |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 1A4E06BE14E0104BDAF8A702E68CAFA792E8DB89 |
| SHA-256 | 84C11538D9CC5A08288A238F7C7B13C42F81B12C9D857687F1961CFB6A00852D |
| Key | Value |
|---|---|
| FileSize | 467472 |
| MD5 | FA5B5736F7912193F2DD41AED9B3ABDC |
| PackageDescription | Google'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. |
| PackageMaintainer | Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org> |
| PackageName | android-libboringssl |
| PackageSection | libs |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 1A4E7E5ABE2737557FF84F481B94B0D236AE3DC4 |
| SHA-256 | F292CAABFE11C95AEF2E53D08A98B406E79815348F8203AFE28C33EB01D711E0 |
| Key | Value |
|---|---|
| FileSize | 545608 |
| MD5 | DC0FA3DE6781E292D08780C161813353 |
| PackageDescription | Google'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. |
| PackageMaintainer | Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org> |
| PackageName | android-libboringssl |
| PackageSection | libs |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 20AF0662B6A1D99C19959D05A3744A5389912E52 |
| SHA-256 | E9616C11931F58605FA709AC0843EA3FD9D54F84CB0200ED17F1F92649B0DBDC |
| Key | Value |
|---|---|
| FileSize | 181732 |
| MD5 | A52AA81511D42A5A27B22E2D8D4EF2F9 |
| PackageDescription | Google's internal fork of OpenSSL for the Android SDK - devel 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 development files. |
| PackageMaintainer | Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org> |
| PackageName | android-libboringssl-dev |
| PackageSection | libdevel |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 21F420A16ED981CD52F9E041595DB46C23B9F538 |
| SHA-256 | 3B41FF6A8F4B054B5AB2B526EE9D4D2F75651D7372800BA3614672302498CD71 |
| Key | Value |
|---|---|
| FileSize | 181728 |
| MD5 | 8161B99FF0E4E3E231A1ECBFC6AF7188 |
| PackageDescription | Google's internal fork of OpenSSL for the Android SDK - devel 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 development files. |
| PackageMaintainer | Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org> |
| PackageName | android-libboringssl-dev |
| PackageSection | libdevel |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 23F6D28C831A95857C1B67C00D883A5B6B46510A |
| SHA-256 | 346E068301EE14E74D675634566D35BCF05983898313D08A95C03B03F71EF300 |
| Key | Value |
|---|---|
| FileSize | 420128 |
| MD5 | ED675CB871B6287A74DF0CCE784CECE3 |
| PackageDescription | Google'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. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | android-libboringssl |
| PackageSection | libs |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 26D561A12666FB43805304531C72A3A040490299 |
| SHA-256 | 21C1D992B260D61A6016732FA0295678BB0F6D44D534D0A1BCE011FBF8FBAC04 |
| Key | Value |
|---|---|
| FileSize | 181376 |
| MD5 | BA2FC3CC73C61A11433F654816139BE7 |
| PackageDescription | Google's internal fork of OpenSSL for the Android SDK - devel 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 development files. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | android-libboringssl-dev |
| PackageSection | libdevel |
| PackageVersion | 8.1.0+r23-2 |
| SHA-1 | 2795E79B0E0CFCA27DCADA1836E4272919B03D11 |
| SHA-256 | 76EBC6A9ADD2521035F8A74B845F8C4BA6775932C8C07FA5E522714AB4C892EA |
| Key | Value |
|---|---|
| FileSize | 534748 |
| MD5 | 527978F1D4E59F7A292072C3A02F6AA3 |
| PackageDescription | Google'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. |
| PackageMaintainer | Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org> |
| PackageName | android-libboringssl |
| PackageSection | libs |
| PackageVersion | 8.1.0+r23-2~18.04 |
| SHA-1 | 2C7E64AD427B366280FE3BB4F3CC6AB0D30FA729 |
| SHA-256 | 1D1C81CABA2BF12D369AB1C10F473108440306A26487ADB93A1D506263EBF0EA |
| Key | Value |
|---|---|
| FileSize | 181916 |
| MD5 | 9C44CC56DB4C7E9D48A7F43E4D2D980A |
| PackageDescription | Google's internal fork of OpenSSL for the Android SDK - devel 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 development files. |
| PackageMaintainer | Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org> |
| PackageName | android-libboringssl-dev |
| PackageSection | libdevel |
| PackageVersion | 8.1.0+r23-2~18.04 |
| SHA-1 | 3CF937382EAB99A192112EB0D522BCD8D07C6F3F |
| SHA-256 | 4DF57210826AAEA75C09813FA657DA8443943055519AF696ACDFC13C95B78E3A |