|author||Adam Langley <firstname.lastname@example.org>||Thu Jan 19 15:12:44 2017 -0800|
|committer||Adam Langley <email@example.com>||Thu Jan 19 23:27:54 2017 +0000|
Remove old ChaCha20-Poly1305 AEAD. Before RFC 7539 we had a ChaCha20-Poly1305 cipher suite that had a 64/64 nonce/counter split (as DJB's original ChaCha20 did). RFC 7539 changed that to 96/32 and we've supported both for some time. This change removes the old version and the TLS cipher suites that used it. BUG=chromium:682816 Change-Id: I2345d6db83441691fe0c1ab6d7c6da4d24777849 Reviewed-on: https://boringssl-review.googlesource.com/13203 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: