|author||David Benjamin <email@example.com>||Sat Oct 10 16:30:22 2015 -0400|
|committer||Adam Langley <firstname.lastname@example.org>||Tue Oct 20 18:16:46 2015 +0000|
Convert ssl3_send_channel_id to CBB. In doing so, simplify the mess around serializing the public key. Channel ID specifies that you write x and y concatenated. Rather than using the X9.62 serialization and chopping bits off, get the affine coordinates and write them out in the same way we write r and s. Also unify the P-256 sanity check around SSL_set1_tls_channel_id and actually check the curve NID. BUG=468889 Change-Id: I228877b736c9722e368d315064ce3ae6893adfc0 Reviewed-on: https://boringssl-review.googlesource.com/6201 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: