Google Git
Sign in
boringssl / boringssl.git / 20d202bb0edae9911fc64c54ba5b045c81a584bb
commit20d202bb0edae9911fc64c54ba5b045c81a584bb[log] [tgz]
authorMatthew Braithwaite <mab@google.com>Tue May 09 10:27:36 2017 -0700
committerCQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>Tue May 09 17:41:17 2017 +0000
tree8a4d79e579babbc04fa9a9ae4c286d42bdfae857
parente838cfb51feb4d56af56ebb2336a5d13b9a58bbd [diff]
unrandom: #define _GNU_SOURCE, for syscall().

This is needed when unrandom.c is compiled on its own.

Change-Id: Ia46e06d267c097e5fa0296092a7270a4cd0b2044
Reviewed-on: https://boringssl-review.googlesource.com/16085
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: Adam Langley <agl@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
1 file changed
tree: 8a4d79e579babbc04fa9a9ae4c286d42bdfae857
  1. .github/
  2. crypto/
  3. decrepit/
  4. fipsoracle/
  5. fuzz/
  6. include/
  7. infra/
  8. ssl/
  9. third_party/
  10. tool/
  11. util/
  12. .clang-format
  13. .gitignore
  14. API-CONVENTIONS.md
  15. BUILDING.md
  16. CMakeLists.txt
  17. codereview.settings
  18. CONTRIBUTING.md
  19. FUZZING.md
  20. INCORPORATING.md
  21. LICENSE
  22. PORTING.md
  23. README.md
  24. STYLE.md
README.md

BoringSSL

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.

There are other files in this directory which might be helpful: