Go to file
David Benjamin e93ffa5da7 Clarify that SSL_get_peer_cert_chain returns the unverified chain.
This came up and I wasn't sure which it was without source-diving.

Change-Id: Ie659096e0f42a7448f81dfb1006c125d292fd7fd
Reviewed-on: https://boringssl-review.googlesource.com/6354
Reviewed-by: Adam Langley <alangley@gmail.com>
2015-10-27 16:42:30 +00:00
crypto Add no-op functions |CRYPTO_malloc_init| and |ENGINE_load_builtin_engines|. 2015-10-27 16:41:40 +00:00
decrepit Fix shared library build on OS X. 2015-10-26 23:39:47 +00:00
include/openssl Clarify that SSL_get_peer_cert_chain returns the unverified chain. 2015-10-27 16:42:30 +00:00
ssl Refactor ChaCha20-Poly1305 AEAD nonce handling. 2015-10-27 01:01:42 +00:00
tool For now, give the unsuffixed ChaCha20 AEAD name to the old version. 2015-10-27 16:39:12 +00:00
util Add the RFC 7539 ChaCha20-Poly1305 AEAD. 2015-10-27 00:46:36 +00:00
.clang-format
.gitignore Fix documentation generation on Windows. 2015-08-19 00:45:42 +00:00
BUILDING.md Add OPENSSL_SMALL. 2015-10-27 16:40:20 +00:00
CMakeLists.txt Add OPENSSL_SMALL. 2015-10-27 16:40:20 +00:00
codereview.settings
LICENSE Note that some files carry in Intel license. 2015-07-28 00:55:32 +00:00
PORTING.md Update PORTING.md for the new renego API. 2015-10-26 19:27:56 +00:00
README.md Links in README.md, take two. 2015-10-13 18:04:43 +00:00
STYLE.md Markdown-ify STYLE. 2015-09-03 18:37:39 +00:00

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.