Google Git
Sign in
boringssl / boringssl / 269416b6e6ddc36d60807fd9cb1892f7c5c0d8ef
commit269416b6e6ddc36d60807fd9cb1892f7c5c0d8ef[log] [tgz]
authorAdam Langley <agl@imperialviolet.org>Thu Apr 17 00:10:33 2025 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 16 17:35:09 2025 -0700
treed25856c434ff17cb94fccb6e70e5724feee3c0f2
parent129da2cf422b964358e82a76ec400914887ed62d [diff]
Update ACVP tests in light of 99bd1df99b

99bd1df99b removed MAC truncation from ACVP but the ACVP tests aren't
run on the commit queue and so I missed updating the tests accordingly.
This change fixes them.

NIST appears to include tests with huge messages and keys now, so the
trimming script it updated to ignore those so that we aren't checking in
megabytes of test vectors.

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