| commit | 0d5bf8d86de1aad51e4740ba4e0335d8792b15af | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Apr 23 16:00:20 2017 -0400 |
| committer | Adam Langley <agl@google.com> | Thu Apr 27 20:26:22 2017 +0000 |
| tree | 33c6a8fafcd212523b59d44a507cdcb91c89a54a | |
| parent | a0cb725b3905c6d596d5adbd7fa2ec034f182b4f [diff] |
Document ERR_error_string_n standalone. Also fully deprecate ERR_error_string. Even when passing an external buffer, passing the length explicitly is better. Change-Id: Id2eb5723410f4564ef5e27c54ba79672133368e7 Reviewed-on: https://boringssl-review.googlesource.com/15424 Reviewed-by: Adam Langley <agl@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.
There are other files in this directory which might be helpful: