|author||David Benjamin <firstname.lastname@example.org>||Wed Dec 09 23:02:39 2015 -0500|
|committer||Adam Langley <email@example.com>||Wed Dec 16 23:34:56 2015 +0000|
Implement draft-ietf-tls-chacha20-poly1305-04. Only ECDHE-based ciphers are implemented. To ease the transition, the pre-standard cipher shares a name with the standard one. The cipher rule parser is hacked up to match the name to both ciphers. From the perspective of the cipher suite configuration language, there is only one cipher. This does mean it is impossible to disable the old variant without a code change, but this situation will be very short-lived, so this is fine. Also take this opportunity to make the CK and TXT names align with convention. Change-Id: Ie819819c55bce8ff58e533f1dbc8bef5af955c21 Reviewed-on: https://boringssl-review.googlesource.com/6686 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: