| commit | b15e56a69486d03996064500e2f06d6a5df5e6a0 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Dec 08 11:20:37 2022 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 09 02:14:02 2022 +0000 |
| tree | c03b25ece303ac12c267953ee340b134ee55294d | |
| parent | 785bb12634b0d2fd39b1e34609bc50366443b67e [diff] |
Add a tool to check whether a binary has an executable stack Plan is: 1. This CL 2. Update the CI/CQ recipe to be able to run this 3. Update the CI/CQ config to enable this on ELF platforms 4. Do not land, but patch out the .note.GNU-stack annotations and -Wa,--noexecstack and confirm CI/CQ fails. Based on manual testing and https://crbug.com/boringssl/292#c4, I anticipate we'll only have coverage on x86 and x86_64 Linux. Currently, our only Arm Linux builders are Android, which use the LLVM linker. The LLVM linker doesn't have this design flaw, so it doesn't need .note.GNU-stack in the first place. It also sounds like GNU ld will make this moot in a future release. 5. Remove -Wa,--noexecstack from crypto/CMakeLists.txt and confirm CI/CQ still passes. Other than generally wanting to test things, the immediate motivation is https://boringssl-review.googlesource.com/c/boringssl/+/55626/1/crypto/perlasm/arm-xlate.pl#b246 Bug: 292 Change-Id: Id1c049bfc2b4e8b7e2c8c32ea6456733a588dfe1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/55645 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@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: