|author||David Benjamin <firstname.lastname@example.org>||Thu Feb 01 15:07:30 2018 -0500|
|committer||Adam Langley <email@example.com>||Thu Feb 01 21:43:42 2018 +0000|
Push an error if custom private keys fail. The private key callback may not push one of its own (it's possible to register a custom error library and whatnot, but this is tedious). If the callback does not push any, we report SSL_ERROR_SYSCALL. This is not completely wrong, as "syscall" really means "I don't know, something you gave me, probably the BIO, failed so I assume you know what happened", but most callers just check errno. And indeed cert_cb pushes its own error, so this probably should as well. Update-Note: Custom private key callbacks which push an error code on failure will report both that error followed by SSL_R_PRIVATE_KEY_OPERATION_FAILED. Callbacks which did not push any error will switch from SSL_ERROR_SYSCALL to SSL_ERROR_SSL with SSL_R_PRIVATE_KEY_OPERATION_FAILED. Change-Id: I7e90cd327fe0cbcff395470381a3591364a82c74 Reviewed-on: https://boringssl-review.googlesource.com/25544 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: