rust: bssl-tls: Clean up the error classification In various context, there is no universal classification of return values of function calls when I/O might have suspended or failed. For instance, we failed to correctly distinguish transport error and TLS error/retry and it has created much difficulty in various internal functions to decide whether the operation is successful or the error should be bubbled up. We are also improperly swallowing transport errors that would have been useful. For DTLS, a failure to send a packet due to system resource pressure is recoverable and the library should pretend that it was successful and allow timeout mechanism to handle this case. Since we have been misclassifying the errors, this has not been working reliably. The best approach so far should have been context-aware, depending on whether we are in a reading or writing or handshaking. Signed-off-by: Xiangfei Ding <xfding@google.com> Change-Id: Ia0092a8acb68bbce2cf7dfa29196d76a6a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/101607 Reviewed-by: 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: