| commit | f4d1d79eeeda22c40be51551f04a2d631a6512dc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jun 15 18:13:32 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 20 03:55:39 2023 +0000 |
| tree | d0c60f24d4e74e413c127771311c2324384488ff | |
| parent | 73dcd474b5bd2dbf21b3cf84dac7c10826e175e7 [diff] |
Simplify shimProcess accept and wait That we pull a value out of a channel and put it back is pretty weird. Also we don't need a select in accept(). It's enough to just close the listener when we learn the child is gone. (That will cancel the Accept call.) Change-Id: If520d9f405fa0b1ad6e3cd23e9ba8a35ff39ba75 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/60887 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: