| commit | a4c8ff01903c56277d4218341e9a68864bc6aea9 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Oct 08 02:49:01 2016 -0400 |
| committer | Adam Langley <agl@google.com> | Sun Oct 09 17:30:32 2016 +0000 |
| tree | 82de28728369687bc0fee86c3b71e7d97d7815db | |
| parent | 43612b6bc742dc4ac242b8e5a10a9f34da29d7d5 [diff] |
Move TLS 1.2 key exchange fields to SSL_HANDSHAKE. SSL_HANDSHAKE is dropped after the handshake, so I've removed the logic around smaller sizes. It's much simpler when we can use CBS_stow and CBB_finish without extra bounds-checking. Change-Id: Idafaa5d69e171aed9a8759f3d44e52cb01c40f39 Reviewed-on: https://boringssl-review.googlesource.com/11567 Reviewed-by: Adam Langley <agl@google.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: