| commit | cc17c248521a1f9c9ffefb7e2f93d1f56b71e6ec | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Mar 30 22:53:03 2017 -0500 |
| committer | Adam Langley <agl@google.com> | Wed Apr 05 22:54:02 2017 +0000 |
| tree | 3fb69896d516152fadb2b48c35a76fb4a061eecc | |
| parent | 6114c3c5d4086d4a0b56c7f6eaa2ebd70d2bea93 [diff] |
Stop pretending RSA and ECDSA sigalgs are configurable. We don't allow consumers to enable and disable RSA and ECDSA signature algorithms but will filter client-sent cipher suites and server-sent client certificate types based on this hard-coded list. This is two less places to update for Ed25519. BUG=187 Change-Id: I62836b6980acc6d03ee254f0a84e9826668e9e57 Reviewed-on: https://boringssl-review.googlesource.com/14567 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.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: