Google Git
Sign in
boringssl / boringssl / 2c27621e854d8d3adcbb9169d9fb0d8484ad1663
commit2c27621e854d8d3adcbb9169d9fb0d8484ad1663[log] [tgz]
authorRudolf Polzer <rpolzer@google.com>Fri Nov 21 05:52:56 2025 -0800
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Dec 15 03:35:01 2025 -0800
tree81326943c6ce063d19c839bde24794a744219fb3
parent53844eb8bb2a6935a77746772657fea96fa1fc9f [diff]
EVP_AEAD: implement sealv/openv for ChaCha20-Poly1305.

Note that for now, the asm optimizations are only available when using
up to 2 plaintext segments or up to 1 ciphertext segment.

Performance note: this seems to cost 14 to 40 CPU cycles per call with
LTO, and 45 to 51 CPU cycles without; no measurable per-byte overhead
though.

Bug: 383343306
Change-Id: I8ebbba3280ac51c200e463b6f71e6e3ed028d450
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/84507
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: Rudolf Polzer <rpolzer@google.com>
Auto-Submit: Rudolf Polzer <rpolzer@google.com>
1 file changed
tree: 81326943c6ce063d19c839bde24794a744219fb3
  1. .bcr/
  2. .github/
  3. bench/
  4. cmake/
  5. crypto/
  6. decrepit/
  7. docs/
  8. fuzz/
  9. gen/
  10. include/
  11. infra/
  12. pki/
  13. rust/
  14. ssl/
  15. third_party/
  16. tool/
  17. util/
  18. .bazelignore
  19. .bazelrc
  20. .bazelversion
  21. .clang-format
  22. .clang-format-ignore
  23. .gitignore
  24. API-CONVENTIONS.md
  25. AUTHORS
  26. BREAKING-CHANGES.md
  27. BUILD.bazel
  28. build.json
  29. BUILDING.md
  30. CMakeLists.txt
  31. codereview.settings
  32. CONTRIBUTING.md
  33. FUZZING.md
  34. go.mod
  35. go.sum
  36. INCORPORATING.md
  37. LICENSE
  38. MODULE.bazel
  39. MODULE.bazel.lock
  40. PORTING.md
  41. PRESUBMIT.py
  42. PrivacyInfo.xcprivacy
  43. README.md
  44. SANDBOXING.md
  45. STYLE.md
README.md

BoringSSL

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: