| commit | 80eb8141a245293e2b133c49d5bc81316317d877 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 23 15:59:26 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 28 18:35:09 2022 +0000 |
| tree | 35aa9911bc01792349dfb16adae11b57b2a3d1ef | |
| parent | 32013e81471bab0b062df48106170bd40b073322 [diff] |
Remove the experimental in-place record APIs. We never ended up using these, or making them work with TLS 1.3 (which has KeyUpdates and NewSessionTickets). It'd still be nice to have an in-place API, but for now unwind these ones until we have time to give it another go. Supporting TLS 1.3's post-handshake messages will probably require a slightly more involved design. (I suspect some of the seal_scatter bits in tls_record.cc can also be simplified with these removed, but I've left them alone here.) Update-Note: Removed some unused, experimental APIs. Change-Id: Iad1245fa467cc6e599d20561f5db44d236219e06 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54527 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: David Benjamin <davidben@google.com> 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: