| commit | 271777f5ac6c7f7d1aaf95b91c5a5bef86da6363 | [log] [tgz] |
|---|---|---|
| author | Brian Smith <brian@briansmith.org> | Sat Oct 03 13:53:33 2015 -1000 |
| committer | Adam Langley <alangley@gmail.com> | Tue Oct 27 01:01:42 2015 +0000 |
| tree | dcba9025f07ba4d5fa83be6acd0f109b8fa42d4a | |
| parent | 3e23e4cb58b4aef45f51b9fabb7953fa4aac9f26 [diff] |
Refactor ChaCha20-Poly1305 AEAD nonce handling. This change reduces unnecessary copying and makes the pre-RFC-7539 nonces 96 bits just like the AES-GCM, AES-CCM, and RFC 7539 ChaCha20-Poly1305 cipher suites. Also, all the symbols related to the pre-RFC-7539 cipher suites now have "_OLD" appended, in preparation for adding the RFC 7539 variants. Change-Id: I1f85bd825b383c3134df0b6214266069ded029ae Reviewed-on: https://boringssl-review.googlesource.com/6103 Reviewed-by: Adam Langley <alangley@gmail.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: