|author||David Benjamin <firstname.lastname@example.org>||Tue Jan 02 16:23:44 2018 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Wed Jan 03 23:03:32 2018 +0000|
Remove some outdated preconditions and postconditions. These date to the old code and have been replaced by the fe and fe_loose bounds in the header file. Also fix up a comment that the comment converter didn't manage to convert. Change-Id: I2e3ea867a8cea2b347d09c304a17e532b2e36545 Reviewed-on: https://boringssl-review.googlesource.com/24525 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: