runner: syncronize shimListener connChan access Concurrent writes and closes on a channel are a data race. The shimListener connChan is written to by the shimDispatcher and closed by the shimListener such that the operations can happen concurrently. There is already a lock on shimListener to set the error and close the channel, so reuse that lock to syncronize the writes to the channel as well. This is slightly slower, but that should be fine. Ideally the write and close operations would be more tightly coupled, but that would require a more significant refactor, the shape of which is not obvious. Change-Id: I534aebacaa3c99a18d34858fa1ca7686727fdada Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88907 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: