| commit | a6b8689dc97c3448d6e73533c2031935ae1edf50 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Tue Jul 25 13:37:51 2017 -0700 |
| committer | David Benjamin <davidben@google.com> | Tue Jul 25 21:41:25 2017 +0000 |
| tree | f56b3bf88403f22405bec20ad7a1ac157bbc516a | |
| parent | 10e10602612bac4d805e6497455fca7f17e6e879 [diff] |
Document our strict behaviour when clients attempt renegotiation. The TLS standard suggests[1] that no_renegotation should be a warning alert and that a client be able to decide whether to continue. This change documents in PORTING.md that BoringSSL responds with a fatal alert instead. This is because we do not want to have any messages that are absorbed without limit in the TLS layer because they may bypass limits implemented at a higher level. We could limit the number of ClientHello messages in the same way that we limit empty records, but we have had this fatal behaviour for a long time without issue and it's simple. (Technically this violates the RFC because the RFC says that no_renegotation is always a warning.) [1] https://tools.ietf.org/html/rfc5246#section-7.2.2 Change-Id: I4d4a696114f7e2b85f39e3fcb7b2c914cef661f2 Reviewed-on: https://boringssl-review.googlesource.com/18409 Reviewed-by: David Benjamin <davidben@google.com>
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: