| commit | be873e9f48b2a07269300282b69bb17d496c69ee | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Wed Feb 08 08:51:25 2017 -0800 |
| committer | David Benjamin <davidben@google.com> | Tue Feb 14 14:49:06 2017 -0500 |
| tree | a397989df03092c3d259198cb9f7a0bdb1137583 | |
| parent | b8684f0276f88d19a14149ae61f3f05d26c5b322 [diff] |
Set output alert when failing to parse public key. Previously, the alert was uninitialised. (Thanks to Robert Swiecki and honggfuzz.) Change-Id: I2d4eb96b0126f3eb502672b2600ad43ae140acec Reviewed-on: https://boringssl-review.googlesource.com/13700 Commit-Queue: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> (cherry picked from commit 7dccc71e08105b100c3acd56fa5f6fc1ba9b71d3)
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: