| commit | 429fdc0d3d787c6f9cc248ee7cb1d5a763b1f277 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jun 17 17:33:30 2016 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Jun 27 18:51:49 2016 +0000 |
| tree | 89074ed73cf29143f7a2a3ca0ee18732a9070cb5 | |
| parent | f0ee9079426169c2796ded90db8ba30f6d2eaedb [diff] |
Simplify ssl3_send_cert_verify's async logic. The only thing we've written before the signature is the hash. We can just choose it anew. This is along the way to getting init_buf out of the handshake output side. (init_buf is kind of a mess since it doesn't integrate nicely with a top-level CBB. Some of the logic hasn't been converted to CBB because they're interspersed with a BUF_MEM_grow.) Change-Id: I693e834b5a03849bebb04f3f6b81f81fb04e2530 Reviewed-on: https://boringssl-review.googlesource.com/8431 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.
There are other files in this directory which might be helpful: