| commit | 779f7d0840a8bac4a0e10f2df4b08cd42df35592 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Aug 26 16:02:49 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 26 21:25:15 2022 +0000 |
| tree | f619efe9f79984ba14c1913c2f2974650504075d | |
| parent | ebd8b8965c74ab06bb91f7a00b23822e1f1f26ca [diff] |
Add an EVP_HPKE_KEM_enc_len API. OHTTP concatenates enc to the ciphertext without any length prefix (unlike ECH), so an implementation would want to know the length of enc for the chosen KEM. Add an accessor to help with that. While I'm here, fix a couple places where we assumed a specific KEM in the HPKE implementation (although we still only support the one KEM so this is all moot). There's probably something to be said for lifting the length checks out of the KEM-specific code and into the wrappers, as we're assuming fixed-width fields anyway. But I've left it alone for now. Change-Id: I634a053faa5e3b35d846b690140333bdc741f92a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54065 Reviewed-by: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@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: