|author||David Benjamin <firstname.lastname@example.org>||Tue Jan 17 14:04:25 2017 -0500|
|committer||Adam Langley <email@example.com>||Tue Jan 17 21:51:06 2017 +0000|
Convert one libssl function to C++11. This is to make sure all of libssl's consumers' have sufficiently reasonable toolchains. Once this bakes, we can go about moving libssl to C++. This is just starting with libssl for now because libcrypto has more consumers and libssl would benefit more from C++ than libcrypto (though libcrypto also has code that would benefit). BUG=132 Change-Id: Ie02f7b0a8a95defd289cc7e62451d4b16408ca2a Reviewed-on: https://boringssl-review.googlesource.com/13161 Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: Adam Langley <email@example.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.
There are other files in this directory which might be helpful: