|author||David Benjamin <firstname.lastname@example.org>||Sat Oct 17 22:59:59 2015 -0400|
|committer||Adam Langley <email@example.com>||Mon Oct 26 18:15:33 2015 +0000|
Deprecate all the string macros. They're really not all that helpful, considering they're each used exactly once. They're also confusing as it is ALMOST the case that SSL_TXT_FOO expands to "FOO", but SSL_TXT_AES_GCM expand "AESGCM" and the protocol versions have lowercase v's and dots. Change-Id: If78ad8edb0c024819219f61675c60c2a7f3a36b0 Reviewed-on: https://boringssl-review.googlesource.com/6307 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: