| commit | 499742c60f84572f0f35454f645606dfcdf79b23 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jul 22 12:45:38 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 27 17:29:23 2017 +0000 |
| tree | 7ebdc652d6e7ebc1d8f4c5e2d5d2eb9e10da3b85 | |
| parent | 6666886a9c782f75f8be7023a05fd733c116ee72 [diff] |
Introduce bssl::Array<T> and use it in SSLKeyShare. An Array<T> is an owning Span<T>. It's similar to absl::FixedArray<T> but plays well with OPENSSL_malloc and doesn't implement inlining. With OPENSSL_cleanse folded into OPENSSL_free, we could go nuts with UniquePtr<uint8_t>, but having the pointer and length tied together is nice for other reasons. Notably, Array<T> plays great with Span<T>. Also switch the other parameter to a Span. Bug: 132 Change-Id: I4cdcf810cf2838208c8ba9fcc6215c1e369dffb8 Reviewed-on: https://boringssl-review.googlesource.com/20667 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: