Result for 0383916FEB5934F3D505CB83CBC5EF36E49809F7

Query result

Key Value
FileName./usr/include/android/openssl/crypto.h
FileSize7664
MD50374BC90F754837F68ED91FA06DD2021
SHA-10383916FEB5934F3D505CB83CBC5EF36E49809F7
SHA-2560366B44E6C2E4596D9DD4DBE523CE6587A17DD5F69BC6EED295DB6B18FCB3E80
SSDEEP96:BKdUiH3eesy13tWTzCS6T28NUCGcfjKgaJPy0PUK6YrzejIErM+e9wjA7/eTe4:A2A31sSMTLI28hZ8tP7EA+mHce4
TLSHT12CF1C6D979A62D730C2263ADD41D0293B755C923BDF0FE82756F680C27F246C11B1B49
hashlookup:parent-total5
hashlookup:trust75

Network graph view

Parents (Total: 5)

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

Key Value
FileSize233060
MD54EB6C31E2C4BD4470128345897B8580A
PackageDescriptionGoogle'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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl-dev
PackageSectionlibdevel
PackageVersion13.0.0+r24-2
SHA-1254D8610B9B750ECB847909BCDC0BFC9CBE9D3AC
SHA-2565CFE3C89DA52F0A82EE54787C38D949F6CE73666F90C532DBC09FF9CD910EB00
Key Value
FileSize233056
MD58DADEEB4EF0FA87EA01E8ED60CD739B4
PackageDescriptionGoogle'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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl-dev
PackageSectionlibdevel
PackageVersion13.0.0+r24-2
SHA-165835B102632EC30DA743128EA69E073827D0B0D
SHA-256B688BBC10EF9BD006744A9F93F7668E361E9B51A70120F04FC9E79F97A1E7973
Key Value
FileSize233060
MD5E1844A646C06B69B81E92F08AC1346A3
PackageDescriptionGoogle'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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl-dev
PackageSectionlibdevel
PackageVersion13.0.0+r24-2
SHA-179A97AA835E3C54729013ADFF13587E3DDF5A387
SHA-25680CE76D262CBD983E252BB8FCF8018036CAED6248A0D24E6D9488BD8A91F4C00
Key Value
FileSize233056
MD5FDD35388CBAA25B2C620FC17E85E43F7
PackageDescriptionGoogle'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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl-dev
PackageSectionlibdevel
PackageVersion13.0.0+r24-2
SHA-1987A598523D0A540FC5584880DE1BE4643FF7DC3
SHA-256935E2424051987589E3A887B2A6A29D27A30A17316C661CF5E9783BD2FD797BD
Key Value
FileSize233060
MD53F032E2D796449DD3B35F60BD93808DC
PackageDescriptionGoogle'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.
PackageMaintainerAndroid Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageNameandroid-libboringssl-dev
PackageSectionlibdevel
PackageVersion13.0.0+r24-2
SHA-14FF165AA9FFD7928525ADED81709A4F97BEE1285
SHA-25637DF503094507A0A8540852D5DDAC3383497A5CF9AEE782862861E1EA32D5047