| commit | e39ac8fb590e47ae8323bd36be07368dea4ca37b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jul 20 12:22:21 2017 -0400 |
| committer | David Benjamin <davidben@google.com> | Thu Jul 20 17:24:12 2017 +0000 |
| tree | 4589e2368e974e1d2cdb5b22fa3475ce9481a4a3 | |
| parent | 1386aad102bfcdadbb7e0911f141067f6d67966d [diff] |
Switch BORINGSSL_INTERNAL_CXX_TYPES in favor of subclassing games. The previous attempt around the 'struct ssl_st' compatibility mess offended OSS-Fuzz and UBSan because one compilation unit passed a function pointer with ssl_st* and another called it with bssl::SSLConnection*. Linkers don't retain such types, of course, but to silence this alert, instead make C-visible types be separate from the implementation and subclass the public type. This does mean we risk polluting the symbol namespace, but hopefully the compiler is smart enough to inline the visible struct's constructor and destructor. Bug: 132 Change-Id: Ia75a89b3a22a202883ad671a630b72d0aeef680e Reviewed-on: https://boringssl-review.googlesource.com/18224 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@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: