| commit | bde00394f0d4d85c9c9f888cf4d47b50dfdca6de | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jun 21 12:19:28 2016 -0400 |
| committer | David Benjamin <davidben@google.com> | Wed Jun 22 13:59:16 2016 +0000 |
| tree | d7413a8c6ed1aa4315644b5abe52133b0af75dfb | |
| parent | 1fd39d84cf616fb126a33b771830477fd321f39e [diff] |
Stop messing with ssl->version before sending protocol_version. This is the only codepath where ssl->version can get a garbage value, which is a little concerning. Since, in all these cases, the peer is failing to connect and speaks so low a version we don't even accept it anymore, there is probably not much value in letting them distinguish protocol_version from a record-layer version number mismatch, where enforced (which will give a version-related error anyway). Should we get a decode_error or so just before version negotiation, we'd have this behavior already. Change-Id: I9b3e5685ab9c9ad32a7b7e3129363cd1d4cdaaf4 Reviewed-on: https://boringssl-review.googlesource.com/8420 Reviewed-by: Steven Valdez <svaldez@google.com> 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: