David Benjamin 97718f1437 Move references to init_buf into SSL_PROTOCOL_METHOD. Both DTLS and TLS still use it, but that will change in the following commit. This also removes the handshake's knowledge of the dtls_clear_incoming_messages function. (It's possible we'll want to get rid of begin_handshake in favor of allocating it lazily depending on how TLS 1.3 post-handshake messages end up working out. But this should work for now.) Change-Id: I0f512788bbc330ab2c947890939c73e0a1aca18b Reviewed-on: https://boringssl-review.googlesource.com/8666 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>		8 år sedan
.github	Add a PULL_REQUEST_TEMPLATE.	8 år sedan
crypto	Define RAND_cleanup in one place only	8 år sedan
decrepit	Make OBJ_NAME_do_all more OpenSSL-compatible.	8 år sedan
fuzz	Replace base64 decoding.	8 år sedan
include/openssl	Push V2ClientHello handling into ssl3_get_message.	8 år sedan
ssl	Move references to init_buf into SSL_PROTOCOL_METHOD.	8 år sedan
third_party/android-cmake	Check in a copy of android-cmake.	8 år sedan
tool	Handle IPv6 literals in bssl client.	8 år sedan
util	Add top-level BUILD file (in util/).	8 år sedan
.clang-format	Import `newhope' (post-quantum key exchange).	8 år sedan
.gitignore	Fix documentation generation on Windows.	9 år sedan
BUILDING.md	Document compiler and assembler requirements.	8 år sedan
CMakeLists.txt	Add top-level BUILD file (in util/).	8 år sedan
CONTRIBUTING.md	Add a CONTRIBUTING.md file.	8 år sedan
FUZZING.md	Replace base64 decoding.	8 år sedan
INCORPORATING.md	Remove backslash.	8 år sedan
LICENSE	Add some bug references to the LICENSE file.	8 år sedan
PORTING.md	Document the d2i object reuse changes in PORTING.md.	8 år sedan
README.md	Add document about incorporating BoringSSL into a project.	8 år sedan
STYLE.md	Update style guide note on files which match OpenSSL.	8 år sedan
codereview.settings	No-op change to trigger the new Bazel bot.	8 år sedan

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
INCORPORATING.md: how to incorporate BoringSSL into a project.
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.