Matthew Braithwaite c5154f7dbc SSL_serialize_handoff: serialize fewer things. In the handoff+handback case, bssl_shim.cc creates 3 \|SSL\| objects: one to receive the ClientHello, one to receive the handoff, and a third one to receive the handback. Before 56986f9, only the first of these received any configuration. Since that commit, all 3 of them receive the same configuration. That means that the handback message no longer needs to serialize as many things. N.B. even before 56986f9, not all of the fields were necessary. For example, there was no reason to serialize \|conf_max_version\| and \|conf_min_version\| in the handback, so far as I can tell. This commit is mechanical: it simply removes everything that doesn't cause any tests to fail. In the long run, I'll need to carefully check for two possibilities: - Knobs that affect the handshake after the server's first message it sent. These are troublesome because that portion of the handshake may run on a different \|SSL\|, depending on whether the handback is early or late. - Getters that may be called post-handshake, and that callers may reasonably expect to reflect the value that was used during handshake. (I'm not sure that either case exists!) Change-Id: Ibf6e0be6609ad6e83ab50e69199e9b2d51e59a87 Reviewed-on: https://boringssl-review.googlesource.com/27364 Commit-Queue: Matt Braithwaite <mab@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com>		6 년 전
.github	Add a PULL_REQUEST_TEMPLATE.	8 년 전
crypto	Don't write out a bad OID	6 년 전
decrepit	fix compilation error for non-english windows (like cjk)	6 년 전
fipstools	Merge NIAP and FIPS test suites.	6 년 전
fuzz	Add a function which folds BN_MONT_CTX_{new,set} together.	6 년 전
include/openssl	Implement TLS 1.3 draft28.	6 년 전
infra/config	CQ: use new luci.boringssl.try bucket.	6 년 전
ssl	SSL_serialize_handoff: serialize fewer things.	6 년 전
third_party	Fix typo in point_add.	6 년 전
tool	Actually benchmark RSA verification with a fresh key.	6 년 전
util	[util] Generate separate GN source sets for headers and sources	6 년 전
.clang-format	Import `newhope' (post-quantum key exchange).	8 년 전
.gitignore	[ndk] Change ndk deps in src and relocate to third_party/boringssl	6 년 전
API-CONVENTIONS.md	Fix API-CONVENTIONS.md typos.	7 년 전
BUILDING.md	Add -DOPENSSL_SMALL to CMake.	6 년 전
CMakeLists.txt	Add -DOPENSSL_SMALL to CMake.	6 년 전
CONTRIBUTING.md	Add a CONTRIBUTING.md file.	8 년 전
FUZZING.md	Fix typo in FUZZING.md.	7 년 전
INCORPORATING.md	Update links to Bazel's site.	8 년 전
LICENSE	Note licenses for support code in the top-level LICENSE file.	6 년 전
PORTING.md	Add cpu-aarch64-fuchsia.c	6 년 전
README.md	Add an API-CONVENTIONS.md document.	8 년 전
STYLE.md	Fix some style guide samples.	7 년 전
codereview.settings	No-op change to trigger the new Bazel bot.	8 년 전
sources.cmake	Add some EC base point multiplication test vectors.	6 년 전

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.
API-CONVENTIONS.md: general API conventions for BoringSSL consumers and developers.
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.