|author||David Benjamin <firstname.lastname@example.org>||Tue Nov 14 10:51:44 2017 +0800|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Nov 14 05:38:48 2017 +0000|
Fix TLSInnerPlaintext limit. See https://github.com/tlswg/tls13-spec/pull/1083. We misread the original text spec, but it turns out the original spec text required senders have version-specific maximum send fragments. The PR fixes this off-by-one issue. Align with the new spec text uniformly. This is a wire format change for our existing drafts *only if* records have padding. We don't currently send padding, so this is fine. Unpadded records continue to be capped at 2^14 bytes of plaintext (or 2^14+1 bytes of TLSInnerPlaintext structure). Change-Id: I01017cfd13162504bb163dd59afd74aff0896cc4 Reviewed-on: https://boringssl-review.googlesource.com/23004 Reviewed-by: David Benjamin <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: