| commit | b3d51be52ffe753a8964a6175f57b5db17425a00 | [log] [tgz] |
|---|---|---|
| author | Nick Harper <nharper@chromium.org> | Fri Jul 01 11:43:18 2016 -0400 |
| committer | David Benjamin <davidben@google.com> | Wed Jul 06 22:24:29 2016 +0000 |
| tree | d0b341bb261399ee262b7d9d1511f715ef528b02 | |
| parent | 17017769084cc5700b4b69ee45d9fe1e3c2d5d3f [diff] |
Split ServerHello extensions into a separate struct. [Originally written by nharper, tweaked by davidben.] In TLS 1.3, every extension the server previously sent gets moved to a separate EncryptedExtensions message. To be able to share code between the two, parse those extensions separately. For now, the handshake reads from serverHello.extensions.foo, though later much of the extensions logic will probably handle serverExtensions independent of whether it resides in ServerHello or EncryptedExtensions. Change-Id: I07aaae6df3ef6fbac49e64661d14078d0dbeafb0 Reviewed-on: https://boringssl-review.googlesource.com/8584 Reviewed-by: David Benjamin <davidben@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: