| commit | 17832275b714570a1c40e6b3a08c27768fc50cf2 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jun 24 16:58:53 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 11 21:28:03 2022 +0000 |
| tree | 0295260dec94ab7bfe487e573fac683ab1ce7301 | |
| parent | 254b8e113977aeb84ced559772537cd15bbe6cfc [diff] |
Replace UTF8_putc with cbb_add_utf8. cbb_add_utf8 is CBB-based, so it is bounds-checked. Change-Id: Ib30272255894d7d3a35a164a5eefcdce9e8e7991 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54646 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@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: