| commit | 32013e81471bab0b062df48106170bd40b073322 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Sep 22 16:55:34 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 28 18:17:59 2022 +0000 |
| tree | 2b78be9edd78055e8920c1e3e4d46a1bf6ca093f | |
| parent | cab31f65f1ad6e6daca62e95b25dd6cd805fce0b [diff] |
Maintain the sequence number as a uint64_t. We spend a lot of effort implementing a big-endian sequence number update, etc., when the sequence number is just a 64-bit counter. (Or 48-bit counter in DTLS because we currently retain the epoch separately. We can probably tidy that a bit too, but I'll leave that for later. Right now the DTLS record layer state is a bit entwined with the TLS one.) Just store it as uint64_t. This should also simplify https://boringssl-review.googlesource.com/c/boringssl/+/54325 a little. Change-Id: I95233f924a660bc523b21496fdc9211055b75073 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54505 Reviewed-by: Bob Beck <bbe@google.com> Reviewed-by: Adam Langley <agl@google.com> 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:
There are other files in this directory which might be helpful: