allwinner_a64/android/external/boringssl/src
2020-07-15 19:27:51 +08:00
..
crypto upload android base code part2 2018-08-08 16:14:42 +08:00
decrepit upload android base code part2 2018-08-08 16:14:42 +08:00
fipstools upload android base code part2 2018-08-08 16:14:42 +08:00
include/openssl upload android base code part2 2018-08-08 16:14:42 +08:00
infra/config upload android base code part2 2018-08-08 16:14:42 +08:00
ssl upload android base code part2 2018-08-08 16:14:42 +08:00
third_party/android-cmake upload android base code part2 2018-08-08 16:14:42 +08:00
tool upload android base code part2 2018-08-08 16:14:42 +08:00
util upload android base code part2 2018-08-08 16:14:42 +08:00
.clang-format upload android base code part2 2018-08-08 16:14:42 +08:00
.gitignore update new sdk 2020-07-15 19:27:51 +08:00
API-CONVENTIONS.md upload android base code part2 2018-08-08 16:14:42 +08:00
BUILDING.md upload android base code part2 2018-08-08 16:14:42 +08:00
CMakeLists.txt upload android base code part2 2018-08-08 16:14:42 +08:00
codereview.settings upload android base code part2 2018-08-08 16:14:42 +08:00
CONTRIBUTING.md upload android base code part2 2018-08-08 16:14:42 +08:00
FUZZING.md upload android base code part2 2018-08-08 16:14:42 +08:00
INCORPORATING.md upload android base code part2 2018-08-08 16:14:42 +08:00
LICENSE upload android base code part2 2018-08-08 16:14:42 +08:00
PORTING.md upload android base code part2 2018-08-08 16:14:42 +08:00
README.md upload android base code part2 2018-08-08 16:14:42 +08:00
sources.cmake upload android base code part2 2018-08-08 16:14:42 +08:00
STYLE.md upload android base code part2 2018-08-08 16:14:42 +08:00

BoringSSL

BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.

Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.

Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.

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.

Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.

There are other files in this directory which might be helpful: