Google Git
Sign in
boringssl / boringssl / 4e3d17a7e7f7105c60d11cc143514855efdb9237
commit4e3d17a7e7f7105c60d11cc143514855efdb9237[log] [tgz]
authorDavid Benjamin <davidben@chromium.org>Thu Dec 31 13:39:02 2015 -0500
committerAdam Langley <agl@google.com>Tue Feb 02 16:23:05 2016 +0000
tree95bed7e2a82647368db08e72e5705e3bd66c926c
parent4aafe6a3af16c577649ad7b8cd94b4635071567b [diff]
Remove redundant logic to compute EC public key.

d2i_ECPrivateKey already computes it as of
9f5a314d35e7eb8be36206f6903a818dfaf24eba.

Change-Id: Ie48b2319ee7d96d09c8e4f13d99de38bfa89be76
Reviewed-on: https://boringssl-review.googlesource.com/6857
Reviewed-by: Adam Langley <agl@google.com>
1 file changed
tree: 95bed7e2a82647368db08e72e5705e3bd66c926c
  1. crypto/
  2. decrepit/
  3. fuzz/
  4. include/
  5. ssl/
  6. tool/
  7. util/
  8. .clang-format
  9. .gitignore
  10. BUILDING.md
  11. CMakeLists.txt
  12. codereview.settings
  13. FUZZING.md
  14. LICENSE
  15. PORTING.md
  16. README.md
  17. STYLE.md
README.md

BoringSSL

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:

  • PORTING.md: how to port OpenSSL-using code to BoringSSL.
  • BUILDING.md: how to build BoringSSL
  • STYLE.md: rules and guidelines for coding style.
  • include/openssl: public headers with API documentation in comments. Also available online.
  • FUZZING.md: information about fuzzing BoringSSL.