| commit | baafa4a653b095f5dd96e9050494e635bd7d8f26 | [log] [tgz] |
|---|---|---|
| author | Martin Kreichgauer <martinkr@google.com> | Tue Aug 09 10:18:40 2016 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Aug 09 17:50:28 2016 +0000 |
| tree | d9a63299bab1785a65d3d666d7168722644273f5 | |
| parent | 14343935b58f3425901aa3ac66f2411c9f8a58bb [diff] |
Undo rename of tlsext_tick_lifetime_hint. It was renamed to ticket_liftetime_hint in 1e6f11a7ff72bea394e6651b512e435fbc95d323, which breaks Qt. Change-Id: I9c6d3097fe96e669f06a4e0880bd4d7d82b03ba8 Reviewed-on: https://boringssl-review.googlesource.com/10181 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: