Google Git
Sign in
boringssl / boringssl / b171749734c438994526096c2150e9baf9d87313
commitb171749734c438994526096c2150e9baf9d87313[log] [tgz]
authorDavid Benjamin <davidben@google.com>Fri Mar 29 17:01:25 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Mar 29 21:48:32 2024 +0000
tree91a1eff18631075f790e2a3818fac092bbf39da7
parenta2ef200d79158613f5a312eb5a13ddceae518bfb [diff]
Switch EVP_CIPHERs to C99 initializers

We're using it in parts of EVP already and this is much more readable.

Change-Id: I42f30b83331cafdabd4f5d995b61176458e906bc
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/67567
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
8 files changed
tree: 91a1eff18631075f790e2a3818fac092bbf39da7
  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: