|author||Adam Langley <firstname.lastname@example.org>||Thu Nov 26 16:39:08 2015 -0800|
|committer||Adam Langley <email@example.com>||Mon Nov 30 22:41:24 2015 +0000|
Work around yaSSL bug. yaSSL has a couple of bugs in their DH client implementation. This change works around the worst of the two. Firstly, they expect the the DH public value to be the same length as the prime. This change pads the public value as needed to ensure this. Secondly, although they handle the first byte of the shared key being zero, they don't handle the case of the second, third, etc bytes being zero. So whenever that happens the handshake fails. I don't think that there's anything that we can do about that one. Change-Id: I789c9e5739f19449473305d59fe5c3fb9b4a6167 Reviewed-on: https://boringssl-review.googlesource.com/6578 Reviewed-by: David Benjamin <firstname.lastname@example.org> 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: