| commit | febf77190f5b32c9825786239f87dfa8a90a9922 | [log] [tgz] |
|---|---|---|
| author | Brian Smith <brian@briansmith.org> | Mon Mar 21 13:47:32 2016 -1000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Dec 16 17:37:03 2016 +0000 |
| tree | 3c58f2b8fa65770b3418cc59828b8de5f6f1d59d | |
| parent | a36255cd4dd2f74e36ee21ac3e33b6120b9d0ae2 [diff] |
Verify consistency of RSA keys after generation & parsing. Call |RSA_check_key| after parsing an RSA private key in order to verify that the key is consistent. This is consistent with ECC key parsing, which does a similar key check. Call |RSA_check_key| after key generation mostly as a way of double-checking the key generation was done correctly. A similar check was not added to |EC_KEY_generate| because |EC_KEY_generate| is used for generating ephemeral ECDH keys, and the check would be too expensive for that use. Change-Id: I5759d0d101c00711bbc30f81a3759f8bff01427c Reviewed-on: https://boringssl-review.googlesource.com/7522 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: