|author||Matthew Braithwaite <firstname.lastname@example.org>||Tue Nov 26 17:49:04 2019 -0800|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Dec 03 00:59:11 2019 +0000|
Move TLS 1.3 state machine constants to internal.h. This benefits TLS 1.3 split handshakes, which need the constants to put an |SSL| into the correct state after SSL_apply_handback(). Change-Id: I2dc5b108d7393fb30708b89c53adcc73056d4f0b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38924 Commit-Queue: Matt Braithwaite <email@example.com> Reviewed-by: David Benjamin <firstname.lastname@example.org>
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: