| commit | c68e5b99a75561fb3fd7e1d4e3f1c82e5f5f170a | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Wed Feb 08 13:33:15 2017 -0800 |
| committer | Adam Langley <agl@google.com> | Thu Feb 09 18:07:30 2017 +0000 |
| tree | 6e5738343f0aa4c65d1f0f577ea9f739e56063cb | |
| parent | 644539191bcdbe8e2758ccddf2cd54a4303e2ac1 [diff] |
Establish that the default value of an out-arg for alerts is SSL_AD_DECODE_ERROR. We already have some cases where the default is DECODE_ERROR and, rather than have two defaults, just harmonise on that. (INTERNAL_ERROR might make more sense in some cases, but we don't want to have to remember what the default is in each case and nobody really cares what the actual value is anyway.) Change-Id: I28007898e8d6e7415219145eb9f43ea875028ab2 Reviewed-on: https://boringssl-review.googlesource.com/13720 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: