How to Install and Uninstall android-libboringssl Package on Ubuntu 20.10 (Groovy Gorilla)
Last updated: November 22,2024
1. Install "android-libboringssl" package
Here is a brief guide to show you how to install android-libboringssl on Ubuntu 20.10 (Groovy Gorilla)
$
sudo apt update
Copied
$
sudo apt install
android-libboringssl
Copied
2. Uninstall "android-libboringssl" package
Here is a brief guide to show you how to uninstall android-libboringssl on Ubuntu 20.10 (Groovy Gorilla):
$
sudo apt remove
android-libboringssl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the android-libboringssl package on Ubuntu 20.10 (Groovy Gorilla)
Package: android-libboringssl
Architecture: amd64
Version: 8.1.0+r23-3
Priority: optional
Section: universe/libs
Source: android-platform-external-boringssl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Android Tools Maintainers
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1631
Depends: libc6 (>= 2.14), libgcc-s1 (>= 3.0), libstdc++6 (>= 4.1.1)
Filename: pool/universe/a/android-platform-external-boringssl/android-libboringssl_8.1.0+r23-3_amd64.deb
Size: 542672
MD5sum: cab10b2201d8ad136ce70621f38d59b3
SHA1: 7cb044b94c85fe52b62cf0f998f41882930255ca
SHA256: b748e53e3321cb99f8c9a1640b043283d4cc9bf4a114c4c3b533d53e05902a58
SHA512: 56e6c4f6da801f44715c705c37bdb9cb0166ee2022944248b32c7616430966a2b1f5450c0b05e1dbfdc68e23747d72ea756f4abe9e40b02b41b7da291cbdd910
Homepage: https://android.googlesource.com/platform/external/boringssl
Description-en: 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.
Description-md5: cd475d5105e77faeb7ea4e52f14b0a97
Architecture: amd64
Version: 8.1.0+r23-3
Priority: optional
Section: universe/libs
Source: android-platform-external-boringssl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Android Tools Maintainers
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1631
Depends: libc6 (>= 2.14), libgcc-s1 (>= 3.0), libstdc++6 (>= 4.1.1)
Filename: pool/universe/a/android-platform-external-boringssl/android-libboringssl_8.1.0+r23-3_amd64.deb
Size: 542672
MD5sum: cab10b2201d8ad136ce70621f38d59b3
SHA1: 7cb044b94c85fe52b62cf0f998f41882930255ca
SHA256: b748e53e3321cb99f8c9a1640b043283d4cc9bf4a114c4c3b533d53e05902a58
SHA512: 56e6c4f6da801f44715c705c37bdb9cb0166ee2022944248b32c7616430966a2b1f5450c0b05e1dbfdc68e23747d72ea756f4abe9e40b02b41b7da291cbdd910
Homepage: https://android.googlesource.com/platform/external/boringssl
Description-en: 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.
Description-md5: cd475d5105e77faeb7ea4e52f14b0a97