| commit | 98e848aa3428b640a9dbcf181fb94f0edf3d38a1 | [log] [tgz] |
|---|---|---|
| author | Shelley Vohr <shelley.vohr@gmail.com> | Wed Sep 18 13:23:30 2019 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 18 21:38:09 2019 +0000 |
| tree | a660d4b3f262221b07f6b14c16768add4f38c594 | |
| parent | 0c4d013916f854e5cc3df1689f6f2ca18a8f8424 [diff] |
Add XOF compilation compatibility flags This CL adds compatibility flags for XOF digests in service of easing compatibility between OpenSSL and BoringSSL. See this logic in Node: https://github.com/nodejs/node/blob/master/src/node_crypto.cc#L4599-L4611 Change-Id: I7f12bed8fb1ea2d9e49dba14ed0c4c819596c70d Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37564 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@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.
Project links:
There are other files in this directory which might be helpful: