Parents (Total: 21)

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

Key	Value
FileSize	483776
MD5	5094C0EFEFC2C735F548CACBEDF44C69
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	10.0.0+r36-1
SHA-1	24C9E99AA2B4130C90A04D859340943B59E124B0
SHA-256	283B00D520F9B058AB48EEEEA5176B13ABFDB85FCC81C7D92DB7F044EB074E81

Key	Value
FileSize	494984
MD5	9443336D1892E8E3924F6F2CCD51CD64
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	10.0.0+r36-2~exp1
SHA-1	250A7DBE49E19693F59F10A87B08F9BACC4A1550
SHA-256	49A0D874D220F3E4C702BB2BCD322CC950FBD9267A80B401E1EDAD5908DC2DDE

Key	Value
FileSize	622784
MD5	DFB58ED1825B3956C82E6101199DAE64
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	10.0.0+r36-2~exp1
SHA-1	305CE20E475ED8D01D14E2946836697D4E1E5197
SHA-256	09C90EBF1706608F9D87C1F49873248B506910AD9EADF7A9749AD74E56B32EC5

Key	Value
SHA-1	320D13638FE2DC11455D09D378E899A0F47885C7
snap-authority	canonical
snap-filename	Zxwd96kEE6Wt0jNX6HUsp1aR6r5uY0RC_17.snap
snap-id	Zxwd96kEE6Wt0jNX6HUsp1aR6r5uY0RC_17
snap-name	mobsf
snap-publisher-id	0bzaPSIkN8wYz66wAtaMAog7IOXvOss9
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2022-10-25T17:29:27.806925Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/Zxwd96kEE6Wt0jNX6HUsp1aR6r5uY0RC_17.snap

Key	Value
MD5	86B8D9B79E3DC054796E69FFBAA6E621
PackageArch	x86_64
PackageDescription	BoringSSL is an implementation of the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, derived from OpenSSL.
PackageMaintainer	https://bugs.opensuse.org
PackageName	libboringssl1
PackageRelease	lp152.2.3
PackageVersion	20190916
SHA-1	3CDD7CF75193770AF15D2AD601416538AD4CFCC4
SHA-256	9FACDB7B6BB72B5A43BF03907EFDF0BA8C7E1BC759852973AA7B65213B5A7689

Key	Value
FileSize	530600
MD5	0CF905BBD9B89C26C10CB75620DCD432
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	10.0.0+r36-2~exp1
SHA-1	507BBA89E4506282D039E5528C18CA3186A3E982
SHA-256	71FD2EE18C226F38A1D41D28E01AEF73DA8179FF04A87D388D4B91F716FE8698

Key	Value
FileSize	622412
MD5	FEAFE486A33F22106092ED2628814385
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	10.0.0+r36-1
SHA-1	5EC80D63FE9B3B13F0ED81B061CCAF0F9D348125
SHA-256	73D77D891B832FEF132BAE6D4108CA29B411D22FA94AC8A1E0E54ACA2858E024

Key	Value
SHA-1	6EB727E9629552C5F85DD366FB8A892BDB5B1C6D
snap-authority	canonical
snap-filename	Zxwd96kEE6Wt0jNX6HUsp1aR6r5uY0RC_8.snap
snap-id	Zxwd96kEE6Wt0jNX6HUsp1aR6r5uY0RC_8
snap-name	mobsf
snap-publisher-id	0bzaPSIkN8wYz66wAtaMAog7IOXvOss9
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2022-10-25T17:29:27.806925Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/Zxwd96kEE6Wt0jNX6HUsp1aR6r5uY0RC_8.snap

Key	Value
FileSize	507884
MD5	9C804DD26D638BC0A9ADFDDABBA01C5A
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	10.0.0+r36-2~exp1
SHA-1	7B21215E599B74E3D47E711B3147007EF21AEE69
SHA-256	839103BCDCA294AEB78BB77B8D3BFB88B7931BDC32B0F81947E7A3A6428A4419

Key	Value
FileSize	494412
MD5	853680B70DCA8FB274832FFC27B2B757
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	10.0.0+r36-1
SHA-1	80B460AB97872A73D5322E92C1DFCB9E6D7042DE
SHA-256	5FB95ACF74CA7DDADD585F4DEF102559D608818F18CB32CA2262DCECCE936117