| commit | cfc11c23209f91eb92fba223d23a7fc0eb3b7bd4 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jul 18 22:45:18 2017 -0400 |
| committer | David Benjamin <davidben@google.com> | Thu Jul 20 03:17:06 2017 +0000 |
| tree | 304a72bca146cfabf918e6b735d80c356a7fff11 | |
| parent | 86e95b852eb4a1e43116cb6951b450b78bd52b4b [diff] |
C++-ify SSL_AEAD_CTX. This adds several utilities as replacements for new and delete and makes bssl::UniquePtr work with our private types. Later work can convert more incrementally. I did this one more aggressively to see how it'd work. Unfortunately, in doing so, I needed to remove the NULL SSL_AEAD_CTX "method" receiver trick to appease clang. The null cipher is now represented by a concrete SSL_AEAD_CTX. The long-lived references to SSL_AEAD_CTX are not yet in types with constructors, so they still bare Delete rather than UniquePtr for now. Though this does mean we may be able to move the sequence number into SSLAEADContext later which is one less object for DTLS to carry around. Bug: 132 Change-Id: I506b404addafb692055d5709b0ca6d5439a4e6be Reviewed-on: https://boringssl-review.googlesource.com/18164 Reviewed-by: Adam Langley <agl@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: