Google Git
Sign in
boringssl / boringssl / 16983d2bc121d71f3262e12cfc2c17cd8f83a1bc
commit16983d2bc121d71f3262e12cfc2c17cd8f83a1bc[log] [tgz]
authorAdam Langley <agl@chromium.org>Tue Jun 17 13:40:32 2025 -0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Aug 08 09:17:45 2025 -0700
treef641f7e31f2f341b29cdabf3ce176378948345c2
parent303d8d7165b74ef44acbcbc0562d3ca2f2726ee8 [diff]
Don't run CTR-DRBG in Kyber tests.

We didn't need to do this, but we ran CTR-DRBG to generate values that
are also in the test vectors and checked that they matched. We will very
likely switch to using a derivation function in CTR-DRBG in the future,
due to NIST's changing requirements, and this will stop working then.

Change-Id: Id7fa678ad602d6a7387158ad84c971aa2121c73f
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79767
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
2 files changed
tree: f641f7e31f2f341b29cdabf3ce176378948345c2
  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: