| commit | 8ed06e0fd07495bf8bdb9ca93a795293f4990d62 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Dec 15 17:00:00 2021 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 16 21:46:55 2021 +0000 |
| tree | 651ccbc4c9217ab36d0002b4f902edd7e1bd3cb7 | |
| parent | 066469055f706aa63aa2c16906332377900f9190 [diff] |
Rewrite bssl_shim command-line parser. The command-line parser is slightly showing its age: first, it is hard to add new integral types, such as uint16_t, which is getting in the way of fixing some of the -Wformat-signedness errors. Second, the parameter extraction logic and skipping logic is duplicated in every type. While I'm here, use a binary search to look up the flag, since we have rather a lot of them. With more C++ template tricks, we could avoid the std::function, but that seemed more trouble than was worth it, especially since, prior to C++17, it's a little hard to convince template argument deduction to infer one of the parameters. Change-Id: I208f89d46371b31fc8b44487725296bcd9d7c8e7 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/50769 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com>
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: