| commit | 6ab7c1482bf4cdc91c87bc512aaf68ffb18975ec | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun May 05 10:34:07 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 07 20:27:53 2024 +0000 |
| tree | 00021ff7536fc0c3e7e72c1089879386cc822e17 | |
| parent | b17231cdb9ec4e877b470c57d3280d9195811cd9 [diff] |
Add tests for some odd escaping behavior in the CONF parser Honestly, these are probably bugs, but add tests for them so, if we change the behavior, we do so intentionally. The escape processing logic has checks for hitting the end of the string early. At first, I had a hard time reaching this case because this is normally processed as a line continuation. However, the line continuation logic is not escape-aware. It just assumes if your line ends "...\\\\", that the last backslash is not a continuation. I.e. it doesn't correctly count escapes. This is almost certainly a bug, but means the escape + EOF behavior is reachable. Even more interesting is that it seems to intentionally terminate quote handling. Add tests for these cases. Change-Id: I9e058ec2b1ce3e20d87eab28a64c79880e3e5cae Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68288 Reviewed-by: Bob Beck <bbe@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: