commit | 1ec335da79eaa8341308acd9dc804078b8593c84 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Oct 04 23:53:36 2022 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 25 21:30:49 2022 +0000 |
tree | 70f82dcf6eff1135410f9cfe911f4124a9f9da70 | |
parent | 7deb8314625b40aea2e0c4fdcf9784d18045e397 [diff] |
Add tests for EVP_PKEY_print_* These are mostly to ensure they don't crash, and that subsequent changes don't unintentionally change the output. The current output is a little weird but, for now, I've just captured the current output, bugs and all. Change-Id: I9f1a4910ccc717764ef44551de9b3e0f9f2a1b40 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54947 Reviewed-by: Bob Beck <bbe@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: