| commit | 659da7c679f07a8e005188394e8a41d9d8a45afe | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Oct 22 15:18:18 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 24 22:32:21 2024 +0000 |
| tree | eef3b5d795c2fbcd263b5f2cddb3f069cb227290 | |
| parent | 781a72b2aa513bbbf01b9bc670b0495a6b115968 [diff] |
Return the record number out of the DTLS record layer For now this is ignored by the caller, but ACK management will require this value. To do this, I've introduced a DTLSRecordNumber type. This isn't quite used in all the places that we could use, so I've left a TODO about this. As part of this, also fix some of the weirdness where some code would mix up seq and epoch+seq across 1.2 and 1.3. Fixing that up also revealed that actually we'd accidentally changed SSL_get_read_sequence slightly in the epoch state refactor. This CL ends up tweaking it slightly more in the DTLS 1.3 case (which doesn't work anyway). I've updated the TODO comment accordingly. Bug: 42290594 Change-Id: Ie7e7da02c432a137ae2314fb3557d1c3717952f3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72271 Reviewed-by: Nick Harper <nharper@chromium.org> Commit-Queue: 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.
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: