|author||David Benjamin <firstname.lastname@example.org>||Mon Jan 22 23:09:16 2018 -0500|
|committer||Adam Langley <email@example.com>||Fri Feb 02 20:16:50 2018 +0000|
Make BN_bn2bin_padded work with non-minimal BIGNUMs. Checking the excess words for zero doesn't need to be in constant time, but it's free. BN_bn2bin_padded is a little silly as read_word_padded only exists to work around bn->top being minimal. Once non-minimal BIGNUMs are turned on and the RSA code works right, we can simplify BN_bn2bin_padded. Bug: 232 Change-Id: Ib81e30ca1e5a8ea90ab3278bf4ded219bac481ac Reviewed-on: https://boringssl-review.googlesource.com/25253 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: