Google Git
Sign in
boringssl / boringssl / 1d24e04c7143171ae2010c842e3e1438510fd1c0
commit1d24e04c7143171ae2010c842e3e1438510fd1c0[log] [tgz]
authorDavid Benjamin <davidben@google.com>Sun May 05 10:34:19 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 10 18:44:51 2024 +0000
tree227d36fad9c3f37cfed7f362c11581f14895ace7
parent8a0da669a08b6c6b805fd7ec9d1e67694fda3711 [diff]
Replace conf_def.h with straightforward functions

We aren't trying to support multiple syntaxes, and most of these table
lookups recognize one or two characters. As the table is unreadable
anyway, this CL was made based on crypto/conf/keysets.pl in upstream
OpenSSL. (See how @V_def is populated in that script.)

Change-Id: Ie38339edabc1dacc49f3efb2bee51d2a026f21fa
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68289
Commit-Queue: Bob Beck <bbe@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
2 files changed
tree: 227d36fad9c3f37cfed7f362c11581f14895ace7
  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. .bazelignore
  15. .bazelrc
  16. .clang-format
  17. .gitignore
  18. API-CONVENTIONS.md
  19. BREAKING-CHANGES.md
  20. BUILD.bazel
  21. build.json
  22. BUILDING.md
  23. CMakeLists.txt
  24. codereview.settings
  25. CONTRIBUTING.md
  26. FUZZING.md
  27. go.mod
  28. go.sum
  29. INCORPORATING.md
  30. LICENSE
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. PORTING.md
  34. PrivacyInfo.xcprivacy
  35. README.md
  36. SANDBOXING.md
  37. 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: