|author||Adam Langley <firstname.lastname@example.org>||Thu Feb 23 16:40:26 2017 -0800|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Sun Feb 26 18:37:53 2017 +0000|
Update AES-GCM-SIV to match revision four of the draft. This change updates AES-GCM-SIV to match revision four of the draft. See  for the reasons behind the changes.  https://tools.ietf.org/html/draft-irtf-cfrg-gcmsiv-04  https://www.ietf.org/mail-archive/web/cfrg/current/msg08895.html Change-Id: Icacfefbd2f470186051551ea227c9d6c6dd6e786 Reviewed-on: https://boringssl-review.googlesource.com/13973 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.org>
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: