Google Git
Sign in
boringssl / boringssl / 02a28c138fcd7e86dd28afaf9719014e89f513f8
commit02a28c138fcd7e86dd28afaf9719014e89f513f8[log] [tgz]
authorBrian Orr <brianorr@google.com>Sat Mar 15 16:20:08 2025 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 17 15:58:45 2025 -0700
treee9b47c61b11a85a79774d193fb3e18435a449a3a
parenta48a41a686d7d601a57fdd1a9ac57ecb7c9ff703 [diff]
[acvptool] Fetch and upload arbitrary algortihms

Support fetching and uploading vectors and results for arbitrary NIST
algorithms. Enabled by removing the algorithm check when parsing the
middleware's advertised configuration. This check still exists prior to
sending test vectors to the middleware for execution.

Change-Id: I77212b414a8f880f57d9834427f98b303ef06e57
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77648
Commit-Queue: Adam Langley <agl@google.com>
Commit-Queue: Brian Orr <brianorr@google.com>
Reviewed-by: Adam Langley <agl@google.com>
1 file changed
tree: e9b47c61b11a85a79774d193fb3e18435a449a3a
  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: