Parents (Total: 50)

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

Key	Value
FileSize	691364
MD5	668A49FDB8575A88DBE2167D8DF63101
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	13.0.0+r24-2
SHA-1	0BD18895E91E3B139E4E5E48D6026150DD751AF4
SHA-256	18E6F45AD02B09AD0D529833D8ECA7EF1E664D85FA943AEFE8256930987D6202

Key	Value
FileSize	70980
MD5	1D031D6AF3EE9FDCF8B63E42BCD669C8
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	11C9257A8D4963D2B611B632DD6CC86BDFAC4594
SHA-256	D1C2A2A200A700A6C0BA3CD1627B83A419F60B5659E990ECBDB549DB832347AF

Key	Value
FileSize	66784
MD5	E29EBC0631C6A5F7FD0891CFD2085FED
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	16A81A95E6DDA7B89D13C63C1E50D916E87196AE
SHA-256	D953406A861EE5F34E437D53B26D09DE915512285424A91B10B158BC182D7A6E

Key	Value
FileSize	65176
MD5	57E50E656D86B9BB77C8D72B747788B4
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	221E119930399689E35B712FF11054EEA6C9200E
SHA-256	D656675E518221CEC323726037EFF8D575000977FEC676711829ADA714203792

Key	Value
FileSize	535720
MD5	BF17346E9072D1A79C6480F58C470CCC
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	13~preview2-5
SHA-1	236240BBEDDA7B6CC599DEA4753EFF3B5B26E266
SHA-256	7E1B04C861C0F023561A92D1FCB9A6DC01D4436E3D5968AEE9CACF8F9038EC23

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	589904
MD5	5B1287381596E88A1F2076717636505B
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	13~preview2-5
SHA-1	2CFB6D89708A5370EE4F3EF4D69C7ED8AB73B4F7
SHA-256	DE593B141E80816DF357B842A8841F82D73148AC86A434399ADC49B3D60FDEBE

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