|author||David Benjamin <email@example.com>||Thu Nov 02 17:21:39 2017 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri Nov 03 16:05:11 2017 +0000|
Add helper functions for SSL_SIGN_*. We end up writing these switch cases everywhere. Let consumers decompose these a bit. The original thought was folks should write switch-cases so they handle everything they support, but that's a pain. As long as algorithm preferences are always configured, we can still add new dimensions because folks won't be asked to sign algorithms that depend on dimensions they don't understand. Change-Id: I3dd7f067f2c55212f0201876546bc70fee032bcf Reviewed-on: https://boringssl-review.googlesource.com/22524 Commit-Queue: David Benjamin <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.org> Reviewed-by: Steven Valdez <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: