| commit | 9f6acfc1f29aa69755b7a9699eb3f6105cb5655c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jul 30 10:29:59 2019 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jul 30 14:53:40 2019 +0000 |
| tree | 6736833da1f117501cca5c03ade5fff669098cfc | |
| parent | 57de2c357b1e23a893b6e3aeef6d3926106e2bf9 [diff] |
Add EVP_PKEY_base_id. OpenSSL has two notions of key type because it supports multiple OIDs for the same algorithm: NID_rsa vs NID_rsaEncryption and five distinct spelling of DSA. We do not support these, so the base ID is simply the ID. Bug: 280 Change-Id: I966530901405a29a0cc35a2bea67304dda336e8a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36844 Reviewed-by: Adam Langley <alangley@gmail.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: