|author||David Benjamin <email@example.com>||Wed Oct 28 14:32:42 2015 -0400|
|committer||Adam Langley <firstname.lastname@example.org>||Wed Oct 28 19:25:36 2015 +0000|
Resolve another ChaCha20-Poly1305 rename deadlock. WebRTC can't roll into Chromium without picking up the iOS build fix, but we can't roll BoringSSL forwards because WebRTC also depends on the previously exposed ChaCha20-Poly1305 cipher suite constants. Define the old constants again. Change-Id: If8434a0317e42b3aebe1bc1c5a58ed97a89a0230 Reviewed-on: https://boringssl-review.googlesource.com/6382 Reviewed-by: Adam Langley <email@example.com>
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: