commit | e57a19203fca0cfe413ad23b08bfce4f8fd59023 | [log] [tgz] |
---|---|---|
author | Adam Langley <agl@google.com> | Wed Nov 04 11:53:46 2015 -0800 |
committer | Adam Langley <agl@google.com> | Wed Nov 04 11:53:46 2015 -0800 |
tree | 01fded45ef3a939f61150f0c31163debabb172d1 | |
parent | c2d3280f0f783caf62c2276a354f6c80ff93c5e9 [diff] |
Add missing newline in aead.h. c2d3280f was missing a newline before the trailer. Change-Id: I0118259b7a8ab15aaaa55125a0f92f3a97794b81
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: