Google Git
Sign in
boringssl / boringssl / 8c6db495c050e4ae9b5ce4673f47ab64c47fe2ee
commit8c6db495c050e4ae9b5ce4673f47ab64c47fe2ee[log] [tgz]
authorDavid Benjamin <[email protected]>Mon Nov 04 16:14:40 2024 +0000
committerBoringssl LUCI CQ <[email protected]>Thu Nov 14 16:25:16 2024 +0000
tree0586e1b4d4185bc19d902397d0989e999a277ffc
parent517b06eb997d7080ff2261fafdfbc43af0f2f709 [diff]
runner: Remove unused SendHalfRTTData option

I forget why we added this. It looks like it's never actually been used.
Half-RTT vs 1-RTT data is not distinguishable from the client, so I
suspect we never actually need to simulate it in the test runner.

Change-Id: I851e2caf417d00da654ee530a240ce54af1415d4
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72888
Reviewed-by: Nick Harper <[email protected]>
Commit-Queue: David Benjamin <[email protected]>
2 files changed
tree: 0586e1b4d4185bc19d902397d0989e999a277ffc
  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. .clang-format
  20. .gitignore
  21. API-CONVENTIONS.md
  22. BREAKING-CHANGES.md
  23. BUILD.bazel
  24. build.json
  25. BUILDING.md
  26. CMakeLists.txt
  27. codereview.settings
  28. CONTRIBUTING.md
  29. FUZZING.md
  30. go.mod
  31. go.sum
  32. INCORPORATING.md
  33. LICENSE
  34. MODULE.bazel
  35. MODULE.bazel.lock
  36. PORTING.md
  37. PrivacyInfo.xcprivacy
  38. README.md
  39. SANDBOXING.md
  40. 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: