| commit | 2f82a0e51b4c944e4047c652ce70ac4987c62a4f | [log] [tgz] |
|---|---|---|
| author | Steven Valdez <svaldez@google.com> | Mon Feb 06 12:06:01 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Feb 06 18:42:53 2017 +0000 |
| tree | 146ce1dfd0c304614286c2fc3806f4f9e831a987 | |
| parent | b7d53ba2684e0b3a97dc6d8c1df3941f7007b4ac [diff] |
Don't stash tlsext_hostname in ssl_get_new_session. ssl_get_new_session would stash a copy of the configured hostname into the SSL_SESSION on the server. Servers have no reason to configuring that anyway, but, if one did, we'd leak when filling in the client-supplied SNI later. Remove this code and guard against this by remembering to OPENSSL_free when overwriting that field (although it should always be NULL). Reported-By: Robert Swiecki <swiecki@google.com> Change-Id: Ib901b5f82e5cf818060ef47a9585363e05dd9932 Reviewed-on: https://boringssl-review.googlesource.com/13631 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
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: