| commit | df08c3a55a8a1b969a7f05813976260cf88ea794 | [log] [tgz] |
|---|---|---|
| author | Rudolf Polzer <rpolzer@google.com> | Fri Jan 16 02:47:59 2026 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 16 11:08:46 2026 -0800 |
| tree | 8d43a8c9eecb93a032a52e4b74b366084d1e536f | |
| parent | 44a1a1f54f8187ef67fb8922eceaf0b841429f9d [diff] |
perlasm scripts: work better if the command interpreter is cmd.exe.
This is done by using newer `perldoc -f open` syntax that provides an
argv list, not a single command string. On Windows this will be
converted into a command string by Perl with proper escaping; on other
systems it'll go directly into argv of the called process.
Also helps on *x in case directory names or similar are evil and contain
quotes (ugh).
Fixes
Can't open perl script "cryptocipherasm../../perlasm/arm-xlate.pl": No such file or directory
when run on Windows from cmd.exe, which stems from backslashes being
interpreted as escapes, not path separators, somewhere along the way.
Bug: 42220000
Change-Id: Ia989572f27bd9e65f05a77fea419b6fc6a6a6964
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/87207
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Auto-Submit: Rudolf Polzer <rpolzer@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:
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: