| commit | dd6fed97046eafe9eb5dbb0a217cfc825a48f9e4 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Fri Oct 23 17:41:12 2015 -0400 |
| committer | Adam Langley <alangley@gmail.com> | Mon Oct 26 17:44:54 2015 +0000 |
| tree | 4505914795be9234ca04004223afe92e2d134484 | |
| parent | 07e138425d8e54d5ca78b395dd808cb5ec3a3eb9 [diff] |
Explicitly handle empty NewSessionTickets on the client. RFC 5077 explicitly allows the server to change its mind and send no ticket by sending an empty NewSessionTicket. See also upstream's 21b538d616b388fa0ce64ef54da3504253895cf8. CBS_stow handles this case somewhat, so we won't get confused about malloc(0) as upstream did. But we'll still fill in a bogus SHA-256 session ID, cache the session, and send a ClientHello with bogus session ID but empty ticket extension. (The session ID field changes meaning significantly when the ticket is or isn't empty. Non-empty means "ignore the session ID, but echo if it resuming" while empty means "I support tickets, but am offering this session ID". The other behavior change is that a server which changes its mind on a resumption handshake will no longer override the client's session cache with a ticket-less session. (This is kind of silly. Given that we don't get completely confused due to CBS_stow, it might not be worth bothering with the rest. Mostly it bugged me that we send an indicator session ID with no ticket.) Change-Id: Id6b5bde1fe51aa3e1f453a948e59bfd1e2502db6 Reviewed-on: https://boringssl-review.googlesource.com/6340 Reviewed-by: Adam Langley <alangley@gmail.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: