| commit | 4df6f11aef5929fc8a0ca9113701d382b02117dd | [log] [tgz] |
|---|---|---|
| author | David Benjamin <[email protected]> | Thu Nov 14 18:07:26 2024 -0500 |
| committer | Boringssl LUCI CQ <[email protected]> | Mon Nov 25 21:09:20 2024 +0000 |
| tree | fc8fed66bb728d8a5830424f414dc877ae9b0e26 | |
| parent | 6f6554fe6fbb7cc18471c15c35bda175a0ce75a8 [diff] |
Test that the DTLS 1.3 server retransmits NewSessionTicket correctly. Testing NewSessionTicket is tricky. First, BoringSSL sends two tickets in a row. These are conceptually separate flights, but we test them as one flight. I've added a mechanism in the testing callbacks to merge two flights together. Second, these tickets are sent concurrently with the runner's first test message. The shim's reply will come in before any retransmit challenges. We need to correct for this in the callback. Bug: 42290594 Change-Id: Id6887c435f7d1d406976377ca66081869e3f1f78 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73230 Commit-Queue: Nick Harper <[email protected]> Reviewed-by: Nick Harper <[email protected]> Auto-Submit: David Benjamin <[email protected]>
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.
Project links:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: