| commit | 82a4b2234ece952a98c653cdcd207d1c02e92009 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Feb 09 17:51:45 2020 -0500 |
| committer | Adam Langley <agl@google.com> | Tue Feb 11 21:38:53 2020 +0000 |
| tree | 9f089af32ce729ea60d7ce8b501cd4cb9cd31706 | |
| parent | f6cc8ddf52ec22596658c2457a41a5c09e3f3b22 [diff] |
Rename TLS-specific functions to tls_foo from ssl3_foo. Some of the TLS-specific functions begin with ssl3_, otherwise with tls_. Align on tls_ since we don't implement SSL 3.0 anymore. (Plain ssl_ means common to TLS and DTLS, which is an odd backronym, but SSL_foo for the APIs are thoroughly stuck.) Change-Id: Ib7acffd21ee370bb9bed46789fb511d00fac24ca Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39985 Reviewed-by: Adam Langley <agl@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.
Project links:
There are other files in this directory which might be helpful: