Google Git
Sign in
boringssl / boringssl / 5f3949e91a3982ee415140979af5e451c358b13c
commit5f3949e91a3982ee415140979af5e451c358b13c[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Dec 10 16:44:32 2025 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Dec 10 20:36:01 2025 -0800
tree34187553a1db9aa68e71f8da24d95ca248e4ccce
parent7ac5099c6b7e86e27f6febe5a02e113073b8a4b2 [diff]
Skip iovec tests for NIST CAVP vectors

The NIST CAVP vectors are a set of 31,000 randomly test vectors imported
from NIST. Multiplicatively testing them against iovec splits takes a
very long time and is of low value becauses NIST's test vectors are
purely random.

Instead, we assume that our normal test vectors provide sufficient
iovec-specific coverage and just run them through the non-iovec APIs to
ensure the overall AEAD implementation matches.

Bug: 383343306
Change-Id: Ib068ef2f75505a103f9462aefcdaac7150509c11
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/85509
Commit-Queue: Rudolf Polzer <rpolzer@google.com>
Reviewed-by: Rudolf Polzer <rpolzer@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
1 file changed
tree: 34187553a1db9aa68e71f8da24d95ca248e4ccce
  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: