commit | 1c6e10495e4f69cf9e5fd4e363d580ff1fdb1a96 | [log] [tgz] |
---|---|---|
author | Patryk Duda <patrykd@google.com> | Fri Apr 12 10:56:28 2024 +0200 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 12 15:53:55 2024 +0000 |
tree | acf4d2f9ee7f69c44963cdf410c867838b131094 | |
parent | bdb7b19c3cd336b9e44086f677a0e37402c4bf13 [diff] |
Disable fork detection for Zephyr and CrOS EC Zephyr and CrOS EC targets embedded devices without MMU unit (no virtual memory). It means that they don't support any address space duplication like fork() or clone(). BUG=b/321092852 Change-Id: Icdf8be888ba87cd164cffb35f1accbc14f1a6887 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/67807 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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: