commit | 6433a91dcb153304da4ef6a3d47a98d5860252a4 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sat May 04 14:17:08 2019 -0500 |
committer | Adam Langley <agl@google.com> | Mon May 06 22:07:21 2019 +0000 |
tree | 263213cf1362db5ef3026188fb8249ca236a1c89 | |
parent | 6477012ff559afcfa911fad81d94fd5e038f5fea [diff] |
Enforce the ticket_age parameter for 0-RTT. For now just hard-code a tolerance of 1 minute. SSL_get_early_data_reason and SSL_get_ticket_age_skew will allow us to tune this. Bug: 113 Change-Id: I85a530494d5405a3e11198d49bfa9cfd355f4f35 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35886 Reviewed-by: Adam Langley <agl@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: