Google Git
Sign in
boringssl / boringssl / 2570b284a4fe517227efe5264dfadb8a48b8c526
commit2570b284a4fe517227efe5264dfadb8a48b8c526[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Oct 08 14:54:04 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Oct 08 19:08:34 2024 +0000
tree1b834df084b6c6f0ec0e6376b41bf52c17e61f4d
parentfa0214602cc5502c2d1e12cc4692d1045a993aba [diff]
Bump the minimum MSVC version to 2022

Per
https://github.com/google/oss-policies-info/blob/main/foundational-cxx-support-matrix.md,
we can require VS2022 or later.

Looking at notable downstreams, Envoy doesn't support Windows at all
anymore, and gRPC raised their minimum in
https://github.com/grpc/grpc/pull/37687

Update-Note: On Windows, MSVC 2022 or later is now allowed. This change
will make the vs2022 configs on CI redundant with the default ones. I'll
remove the redundant ones after this lands.

Change-Id: Ib740e091271c94e0ef8999e61a31a8e3df63f349
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71830
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Bob Beck <bbe@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
3 files changed
tree: 1b834df084b6c6f0ec0e6376b41bf52c17e61f4d
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. pki/
  11. rust/
  12. ssl/
  13. third_party/
  14. tool/
  15. util/
  16. .bazelignore
  17. .bazelrc
  18. .clang-format
  19. .gitignore
  20. API-CONVENTIONS.md
  21. BREAKING-CHANGES.md
  22. BUILD.bazel
  23. build.json
  24. BUILDING.md
  25. CMakeLists.txt
  26. codereview.settings
  27. CONTRIBUTING.md
  28. FUZZING.md
  29. go.mod
  30. go.sum
  31. INCORPORATING.md
  32. LICENSE
  33. MODULE.bazel
  34. MODULE.bazel.lock
  35. PORTING.md
  36. PrivacyInfo.xcprivacy
  37. README.md
  38. SANDBOXING.md
  39. 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: