David Benjamin fda22a7573 Reimplement DSA parsing logic with crypto/asn1. Functions which lose object reuse and need auditing: - d2i_DSA_SIG - d2i_DSAPublicKey - d2i_DSAPrivateKey - d2i_DSAparams BUG=499653 Change-Id: I1cc2ae10e1e77eb57da3a858ac8734a95715ce4b Reviewed-on: https://boringssl-review.googlesource.com/7022 Reviewed-by: Adam Langley <agl@google.com>		vor 8 Jahren
crypto	Reimplement DSA parsing logic with crypto/asn1.	vor 8 Jahren
decrepit	Tweaks for node.js	vor 8 Jahren
fuzz	Update the fuzz tests for the server.	vor 8 Jahren
include/openssl	Reimplement DSA parsing logic with crypto/asn1.	vor 8 Jahren
ssl	Use initializer lists to specify cipher rule tests.	vor 8 Jahren
tool	Make it possible to tell what curve was used on the server.	vor 8 Jahren
util	Have doc.go parse struct comments.	vor 8 Jahren
.clang-format	Inital import.	vor 10 Jahren
.gitignore	Fix documentation generation on Windows.	vor 9 Jahren
BUILDING.md	Updating BUILDING.md for windows.	vor 8 Jahren
CMakeLists.txt	Prefer MSVC over GCC if both are in %PATH%.	vor 8 Jahren
CONTRIBUTING.md	Add a CONTRIBUTING.md file.	vor 8 Jahren
FUZZING.md	Update and fix fuzzing instructions.	vor 9 Jahren
LICENSE	Note that some files carry in Intel license.	vor 9 Jahren
PORTING.md	Document the d2i object reuse changes in PORTING.md.	vor 8 Jahren
README.md	Add a CONTRIBUTING.md file.	vor 8 Jahren
STYLE.md	Update link to Google style guide.	vor 9 Jahren
codereview.settings	Add a codereview.settings file.	vor 10 Jahren

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.
CONTRIBUTING.md: how to contribute to BoringSSL.