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().


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>
1 file changed
tree: acf4d2f9ee7f69c44963cdf410c867838b131094
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. gen/
  7. include/
  8. pki/
  9. rust/
  10. ssl/
  11. third_party/
  12. tool/
  13. util/
  14. .clang-format
  15. .gitignore
  18. build.json
  19. BUILDING.md
  20. CMakeLists.txt
  21. codereview.settings
  23. FUZZING.md
  24. go.mod
  25. go.sum
  28. PORTING.md
  29. PrivacyInfo.xcprivacy
  30. README.md
  32. STYLE.md


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: