| commit | e8703a37085ca1205d202a95a7115281159849e6 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Jul 09 16:17:55 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jul 12 20:54:02 2017 +0000 |
| tree | 84bc73bc349347fa94567a178f31faa12e2d1605 | |
| parent | a93a68d3cd551fb2d71a72e9915c589ea2d4f672 [diff] |
Switch a number of files to C++. http://i1.kym-cdn.com/photos/images/original/000/242/631/382.gif In the first step, switch C files to C++ individually, keeping everything in internal.h C-compatible. We'll make minimal changes needed to get things compiling (notably a lot of goto errs will need to turn to bssl::UniquePtr right away), but more aggressive changes will happen in later steps. (To avoid a rebase, I'm intentionally avoiding files that would conflict with CLs in flight right now.) Bug: 132 Change-Id: Id4cfd722e7b57d1df11f27236b4658b5d39b5fd2 Reviewed-on: https://boringssl-review.googlesource.com/17667 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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:
