Google Git
Sign in
pigweed / third_party / boringssl / boringssl / refs/heads/main
commitd8d1c6a2d034df2a62bcf75604a4824f0e20e19e[log] [tgz]
authorRoland Shoemaker <bracewell@google.com>Mon Apr 22 10:55:47 2024 -0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 22 23:43:45 2024 +0000
tree7fdd93817d34d77badec5f969c1cad0b28158b43
parentb62a6e6eeb05b9db60bb6ef7adc2c093250ad0a5 [diff]
Change unsupported KEM identifier

To a definitely not real one. Otherwise tests fail if you do actually
support DHKEM(P-256, HKDF-SHA256).

Change-Id: Icb60458bba94e8df1954f154f5f6c9965543af45
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/67927
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Roland Shoemaker <bracewell@google.com>
1 file changed
tree: 7fdd93817d34d77badec5f969c1cad0b28158b43
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. gen/
  7. include/
  8. pki/
  9. rust/
  10. ssl/
  11. third_party/
  12. tool/
  13. util/
  14. .clang-format
  15. .gitignore
  16. API-CONVENTIONS.md
  17. BREAKING-CHANGES.md
  18. build.json
  19. BUILDING.md
  20. CMakeLists.txt
  21. codereview.settings
  22. CONTRIBUTING.md
  23. FUZZING.md
  24. go.mod
  25. go.sum
  26. INCORPORATING.md
  27. LICENSE
  28. PORTING.md
  29. PrivacyInfo.xcprivacy
  30. README.md
  31. SANDBOXING.md
  32. 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:

There are other files in this directory which might be helpful: