| commit | 78c88c999ebd2a462ed9cf67b77a5970ab6e684a | [log] [tgz] |
|---|---|---|
| author | Kris Kwiatkowski <kris@cloudflare.com> | Mon Mar 11 14:40:59 2019 +0000 |
| committer | Adam Langley <agl@google.com> | Fri May 24 16:52:33 2019 +0000 |
| tree | 94b4674a9e1acfcd74250058ace284a9e0796487 | |
| parent | 6676b9ad1ad2a8b40ed187f67ca9286ed65fc50e [diff] |
Integrate SIKE with TLS key exchange. Implements support for hybrid key exchange based on SIKEp503, a post quantum, isogeny based KEM. This is a hybrid construction mixed with X25519 key agreement. Code point is 0xFE32. Cloudflare's SIDH implementation is used for testing. Key exchange can be used with TLS1.3 only. Change-Id: I3a5f38d6f7d016274e5bcfb629249664e1d983eb Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35264 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: