Parents (Total: 37)

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

Key	Value
FileSize	196672
MD5	A33CB737CDCD1850D2BCA94612A793D6
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	10.0.0+r36-2~exp1
SHA-1	07E03767080BF32FF153921D979A30E921E99528
SHA-256	6CCFBC49D0DE291CACB233FA9EC8FF961FBB5001D3DAC6C56D6DD97C9388767E

Key	Value
FileSize	196668
MD5	2D66790F147E45051A7E1B6C07FE4D81
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	10.0.0+r36-2~exp1
SHA-1	0A85FB6565603A625F1F37208C0CDE784AA261C4
SHA-256	56E583602F779EEF273D41F7955B391E008611EEBCCC0CD834F59E6260134749

Key	Value
FileSize	196668
MD5	459F471EDACED4DDCCCE670CF0204030
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	10.0.0+r36-2~exp1
SHA-1	2349AEC390BB83E0D82E98CFA88FBB321A6D667D
SHA-256	C21F6AB364A994516AC45CB45328EB589DDFE3659A34F959B8F47510C7E9CDF9

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
FileSize	196572
MD5	018FC7738D705924EF964C83D1760FBA
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	10.0.0+r36-1
SHA-1	32076B022226B02EB00B211EE0C50347EA125303
SHA-256	EFDA2BF8FF82C655CB531191D5182F028509997AEF2DF7756E69DBA2562D754B

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
FileSize	196572
MD5	B462E1817734B6970617E93F8A346B7E
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	10.0.0+r36-1
SHA-1	4F58DB3F36362F7808DEC6EDC83572B1530FF0E3
SHA-256	18FBD539DE4B7953144AEDC4A90BE2971768D78EE213E358901BC99ADE649C76

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